Global Do NOT save / change a database until user approves

I would like to know if there is a Global method - similar to Excel, Word,
etc. that will ask the user: "Do you want to save changes?"... so that the
database won't change unless approved by the user.
--
Glenda

"Glenda" wrote in message
...
I would like to know if there is a Global method - similar to Excel, Word,
etc. that will ask the user: "Do you want to save changes?"... so that the
database won't change unless approved by the user.

No.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

"Rick Brandt" wrote in message
...
"Glenda" wrote in message
...
I would like to know if there is a Global method - similar to Excel,
Word,
etc. that will ask the user: "Do you want to save changes?"... so that
the
database won't change unless approved by the user.

No.

I just thought I should expand on this response.

With Word or Excel the entire file is loaded into RAM when you open it so
it is easy for you to make extensive changes (all in RAM) and then be asked
to save when you are closing the file. An Access file is NOT loaded
completely into memory. Bits are retrieved from disk when required and
they are written back to disk as soon as is practical.

This is for two reasons. One, an MDB file can easily become large enough
that you would never want to load the entire thing into memory even if you
could, and second is concurrency issues.

Access out-of-the-box is set up assuming multiple users might be accessing
the data at the same time. If a user worked with the entirety of the
database in memory and only committed the changes to disk when closing the
file this would be all well and good if no one else also was using the
file. As it is Access has to deal with the possibility of multiple users
trying to work with the same data.

The record locking scheme used has to make compromises between denying
access to records that others are using or having to deal with possible
conflicts if it allows them both to have the data. This is a thorny enough
issue at the record or page level, so you can imagine what a nightmare it
would be if the entire database had to be either locked or reconciled when
multiple users committed their changes.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Glenda wrote ...

I would like to know if there is a Global method - similar to Excel, Word,
etc. that will ask the user: "Do you want to save changes?"... so that the
database won't change unless approved by the user.

At the start of the session, begin a transaction. At the end of the
session, show you "Do you want..?" message and either commit or
rollback your transaction as appropriate.

Jamie.

--

"Rick Brandt" wrote

With Word or Excel the entire file is loaded into RAM when you open it so
it is easy for you to make extensive changes (all in RAM) and then be asked
to save when you are closing the file.

When you open an Excel .xls file, a copy is made in the same folder as
the original (this is why it is not a good idea to work on an Excel
workbook from a floppy disk e.g. there may not be enough space for a
copy to be made). The original is flagged as read only. If the user
does not save their work, the copy is removed.

Jamie.

--