Originally Posted by
vientito
...I don't suppose it will work in unbound form since there is no initial recordset...
In point of fact there is no Recordset at all...initial or otherwise...ever! An Unbound Form contains no Records. It's merely a collection of Controls for entering data. There is nothing to refresh.
Why do you 'have to work' with an Unbound Form?
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
The question here is "Why?" Why do you not want Access to automatically save the Record by default? There's nothing that can be done using Unbound Forms that cannot be accomplished with Bound Forms, and usually accomplished with less work!
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007