Stop Access from creating new record when inputting data in field or tabing

[basshead22]

Hello All,

How do you prevent access from adding a new record when u input data in the current record or tab to the next field? My database is set up to open with a form where the user picks his name and then a week ending date once that is complete u open a new form where the name and date auto populate along with other fields to fill out such as job charge, charge type , times charged for each day of the week. But I don't want access to create a new record everytime the person inputs or tabs..... .:banghead:

HELP PLEASE!!!!!!!!!

I have attached my database for better clarity!

 

[spikepl]

play with Form's Property Sheet> Other>Cycle

 

[basshead22]

Thanks spikepl I did try that still adding new record.

 

[spikepl]

Then play some more, because that is what can fix your predicament. That is unless you have code that goes to new record buried somewhere

 

[basshead22]

Nope no code!! I shall try again!

 

[basshead22]

Still didn't work!!!

 

[JHB]

Set the form's property "Allow Additions" to "No".

 

[missinglinq]

If you are using a Continuous or Datasheet View Form, and have it set up to allow New Records to be added, when you start to enter a New Record, Access is going to display the Controls for another Record; that's how it works! If you set AllowAdditions to No, it won't do this, but you then cannot add New Records!

Notice that I said: "Access is going to display the Controls for another Record." Access is not creating another Record, merely placing the Controls there if you want to add another Record! If you close the Form after entering your Current Record, the 'blank Record' is not saved to the Table.

The only way to circumvent this default behavior is to use an Unbound Form for entering a New Record, and this prevents you from seeing existing Records. Also, using an Unbound Form means that the developer has to write code to do everything they need done; Access will do virtually nothing without you coding it, and this is not a task for the Access newbie! I've been developing Access databases for almost 15 years and would only use an Unbound Form if there was an absolutely, positively critical job to be done that couldn't be done with a Bound Form, and in all those years I, personally, haven't come across such!

BTW, spikepl's suggestion of changing the Cycle Property to Current Record will prevent the Tabbing out of the last Control from moving you into that 'New Record,' it just won't prevent the 'new' line from appearing when you enter that first character into your Current/New Record.

Linq ;0)>

 

[basshead22]

Thank you Missinglinq! My mistake I thought by it moving to the new record it was saving a blank record with just my auto name and week ending but u are right it just sets u up for a new record. Thank u for your time! and I will keep in mind the cycle property. I made a lot of progress today on my DB thank you all!

 

[missinglinq]

You're quite welcome; that's why we're all here!

And don't feel bad! I've been posting here, and on half-a-dozen other Access sites, for eight years, now, and I've seen this question at least once a week, every single week of those eight years!

Linq ;0)>