Need help with Forms

[mpasta]

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?

 

[Jon]

Welcome to Access World! We're so happy to have you join us as a member of our community. As the most active Microsoft Access discussion forum on the internet, with posts dating back more than 20 years, we have a wealth of knowledge and experience to share with you.

We're a friendly and helpful community, so don't hesitate to ask any questions you have or share your own experiences with Access. We're here to support you and help you get the most out of this powerful database program.

To get started, we recommend reading the post linked below. It contains important information for all new users of the forum:

https://www.access-programmers.co.uk/forums/threads/new-member-read-me-first.223250/

We hope you have a great time participating in the discussion and learning from other Access enthusiasts. We look forward to having you around!

 

[Gasman]

Yes, set Data Entry to Yes.
Not what I would recommend though.

 

[LarryE]

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:
DoCmd.GoToRecord acActiveDataObject, , acNewRec

 

[moke123]

use the datamode argument of the open form method

https://learn.microsoft.com/en-us/office/vba/api/access.docmd.openform

DoCmd.OpenForm "frmCaseDetail", , , "CaseID = " & Me.CaseID, acFormAdd

you can then use the same form to add or edit data depending on the argument used.

 

[mpasta]

Yes, set Data Entry to Yes.
Not what I would recommend though.

why don't you recommend this?

 

[mpasta]

I should have mentioned I am quite the novice in Access. I am using the wizards to create most of this...

 

[Gasman]

why don't you recommend this?

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.

 

[LarryE]

Can 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.

 

[mpasta]

Can 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 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

 

[mike60smart]

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

I must agree with Gasman's suggested method.

 

[Gasman]

Then when the logic changes in the Add form, you need to apply the same to the Edit form?

 

[moke123]

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?
Why have 2 forms when one will suffice? There's a reason Microsoft included the DataMode argument in the open form method.

There are many ways to idiot proof forms. Here's my example from above but I added a button that Unlocks or locks a form from accidentally being edited.

 

[Isaac]

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.

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).

 

[moke123]

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).

That can also be coded into the single form with user levels.

 

[theDBguy]

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?

Hi. Welcome to AWF!

Were you able to solve your issue? Did you try any of the suggestions?

 

[Isaac]

That can also be coded into the single form with user levels.

Of course that's true, I just like the design of my system to reflect the business processes and decision making in the real world

 

[mpasta]

Hi. Welcome to AWF!

Were you able to solve your issue? Did you try any of the suggestions?

Not really

 

[Gasman]

Not really

Well post #3 will do exactly what you want.

You have to do some work yourself you know. We are here to help, not serve.

 

[mpasta]

How can we help you if you don't try the suggestions or provide helpful information? If you look at #10, I explained how you can use the same form but open it in add mode or edit mode. It isn't what I do. I explained that later but it will allow you to use a single form for both data entry and update. You just have two open buttons. One for add and one for edit and use the options of the OpenForm Method to control how the form opens.

Let's not assume that I don't want or have not tried the suggestions listed. I explained that I am quite the novice with this and instead maybe assume that I still do not quite understand how to implement the suggestions. Be kind.