I have a problem where if the staff press enter key on a data entry form (the form is to create a new record) it seems to move direct to a new record - is there a solution to this?
I have a problem where if the staff press enter key on a data entry form (the form is to create a new record) it seems to move direct to a new record - is there a solution to this?
Access 2010 has settings that can change that will affect how the client behaves. Also, the form's property settings have options. I think there is one about tab to new record or that one may be in the global client settings.
You mean if, after entering data in the last Control on the Form, they hit <Enter>. For the Form, itself, go to Properties - Other and change the Cycle Property from All Records to Current Record.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
Well the idea is that they complete that record and only that record. Sometimes they might happen to use enter instead of tabas they go through the fields and it then swaps everything in the subform to blank. I have some vba on "on enter" on the subform but I doubt that has anything to do with it... right?
Sorry, can't really understand what you're saying, here. Usually when posters complain of being taken to a new record, when tabbing through a record, it's the results of the Cycle Property being set as I indicated. You now mention a subform, which your original post didn't; is this happening on the main form or the subform? I think a little more explanation is needed.
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
It's happening on the subform. The main form is a data entry form, then the subform is connected.Sorry, can't really understand what you're saying, here. Usually when posters complain of being taken to a new record, when tabbing through a record, it's the results of the Cycle Property being set as I indicated. You now mention a subform, which your original post didn't; is this happening on the main form or the subform? I think a little more explanation is needed.
So, on the Form being used as the basis for the Subform, have you checked the Cycle Property, as per Post #3?
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
As I told you, in Post #3, change it to Current Record!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
Seems to fix. I don't understand the whole cycle things but I guess this is required for all subforms that are tied 1 - 1?
Nope! The Cycle Property is part of all Forms, regardless of whether or not they're an independent Form, a Main Form or a Subform. It goes back to the early days of data entry, I guess, when a gazillion records were entered at once, and it was advantageous to hit <Enter> or <Tab>, when at the end of one Record, and go to the next New Record.
Glad it's working for you!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
wha wait. Should I be making it standard on all forms not to cycle all records then?Nope! The Cycle Property is part of all Forms, regardless of whether or not they're an independent Form, a Main Form or a Subform. It goes back to the early days of data entry, I guess, when a gazillion records were entered at once, and it was advantageous to hit <Enter> or <Tab>, when at the end of one Record, and go to the next New Record.
Glad it's working for you!
Linq ;0)>