Sorry, but your explanation is fuzzy, to say the least, and telling you "
Why is this different from every other time?" is totally impossible, since you haven't told us
how you've done this. Because of this, the following are some general observations and guesses as to how you're trying to do this.
Is this a
Bound Form or an
Unbound Form? With a
Bound Form, if the
Form is based on a
Query, when a
Record is
Created or
Edited and the
Record is saved (which it is if you move to any other
Record or
Close the
Form) the
Query and the underlying
Table are updated at the same time. There is no need, in an Access database with
Bound Forms, to have a '
Save' button.
The only thing needed to allow multiple users to access the same
Tables, Forms, Queries and
Reports, at the same time, is for the app to be
Split into a
Back End, holding the
Tables/Data, and a
Front End, holding everything else.
A
single copy of the
Back End is stored on a
shared drive, and a
Copy of the
Front End is placed on
each user's PC.
If this is an
Unbound Form, it is very, very seldom that they are needed in Access. They aren't needed to
Validate Data, before saving, nor to allow
Multiple -Users, the most common reasons given for using them.
A big part of the reason to use Access for database development is the speed with which it can be created, using
Bound Forms. Several developers I know, experienced in Visual Basic database development and Access development, estimate that development, using
Unbound Forms, by
highly experienced developers, takes twice as long as it does when using Access and
Bound Forms.
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 if far, far better than anything you can do in Access
Linq
;0)>
