You cannot have a Continuous View, Unbound Form! An Unbound Form actually has no Records, only Controls to enter data. With a Bound Form, as with a Table, as ranman256 mentioned, leaving a given Record automatically saves that Record.
Using Unbound Forms really does away with the basic function of Access, which is to facilitate RAD (Rapid Application Development) and should only be attempted by very experienced Access developers, and then only when/if a legitimate purpose requires it, and most situations don’t!
Several developers I know, experienced in Visual Basic database development and Access development, estimate that development, using Unbound Forms, by highly experienced developers, takes two to three times as long, using Unbound Forms, as it does when using Access and Bound Forms. That’s because with Bound Forms the Access Gnomes do the vast majority of the heavy lifting; with Unbound Forms the developer has to write code for everything...even the most mundane tasks!
The only workaround, for this kind of thing, would be using a Form that is Bound to a temporary Table, and then appending the Records to the permanent Table...and after twenty plus years of developing Access databases, that involves more programming than I'd care to do, for this reason!
If you insist on using Unbound Forms, you'd be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.
- You can create an EXE file which gives total protection to your code/design
- You can distribute the db to PCs without a copy of Access being on board
- Your data security is far, far better than anything you can do in Access
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007