Good morning! I am creating a Form for the first time to use with our database as a way to enter new members. Is there a way to have the form always open to a new record instead of opening with data already there from the table?
Using the form On Load Procedure Event enter the following line of code:Good morning! I am creating a Form for the first time to use with our database as a way to enter new members. Is there a way to have the form always open to a new record instead of opening with data already there from the table?
DoCmd.OpenForm "frmCaseDetail", , , "CaseID = " & Me.CaseID, acFormAdd
why don't you recommend this?Yes, set Data Entry to Yes.
Not what I would recommend though.
Because it would drive me around the bend if every time I opened a form it meant I had to add a record.why don't you recommend this?
I have the table built. It is a table to store our student data. The form would only be used to add new students; not for any other purpose which is why I would like it to open with a blank record each time so that our users never accidentally type over a current student's dataCan you describe the overall purpose of this ACCESS application and what you want to keep track of with it? The building of the table design comes first, before anything else, including building forms and reports.
I must agree with Gasman's suggested method.I have the table built. It is a table to store our student data. The form would only be used to add new students; not for any other purpose which is why I would like it to open with a blank record each time so that our users never accidentally type over a current student's data
What does your user do if after entering a new student they realize they made a typo? Or entered a duplicate student?The form would only be used to add new students; not for any other purpose which is why I would like it to open with a blank record each time so that our users never accidentally type over a current student's data
Because it would drive me around the bend if every time I opened a form it meant I had to add a record.
I would have a form that allowed me to read/edit and add records. Not one to add and another to read/edit.
If you create a form to do all three, then there are navigation buttons as the bottom and the * allows you to create a new record. I have always used the Access native functionality when possible. My users never complained.
That can also be coded into the single form with user levels.However there is one scenario where separating them is a good idea: Where the job function of the end-users differs by the same category separating the forms. (which mine usually have-one person doing heads down data entry and another , maybe one manager, who has the authority to edit).
Hi. Welcome to AWF!Good morning! I am creating a Form for the first time to use with our database as a way to enter new members. Is there a way to have the form always open to a new record instead of opening with data already there from the table?