Originally Posted by
Remster
...As soon as you type a character in the new record...a second new record appears...
You have to understand that you're not actually seeing a 'new Record!' While the Access Gnomes have presented what appears to be a new Record, it's actually only framework for a new Record, if you will! It will only become a new Record if, once again, you enter a single character into one of its Controls!
To keep your user from moving to a new Record, before completing their current Record, you need to have validation, insuring that all Controls, in the current Record, are populated/saved first.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007