Forcing a requery

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I posted a question yesterday and I did receive a reply,
however I am still curious if there is a way to force a
requery on another session? Below is the original
question, reply and follow up question. If anyone has any
suggestions, I would be forever grateful!!



OriginalQuestion: I have written a application that is on
a network. Multiple people will be using it
simultaneously. How can I requery all sessions when each
user adds or changes a record?


Reply: Did you split the database and deploy to each user
their own copy of the
frontend? Are all the users linked to the same backend? If
so, then access
should handle this for you.

Next Question: no I didn't split the datebase or give each
user their own copy. Is splitting the database the only
option I have to refresh all sessions? Are there other
advantages to splitting a database into a front end and
then a backend.
I have noticed that I have had connection problems when I
have done this in the past. After reading the help files
regarding "split", the users can change their front end,
which I do not want to allow!
 
Splitting a database is practically obligatory for multiple users. It has
numerous advantages. It means that you can continue to develop the database
front end without stopping everyone working on the application. It allows
you to create temporary tables in the front end, or modify query defs -
things that would cause chaos if done in a shared file.

The front end is generally a MDE file, and the users cannot modify forms,
reports or modules in these. You should also hide the database window, and
you can disable the shift key during startup to prevent the users from
getting access to it. That should keep them out of the tables and queries
too. With a split database the users could only modify tables from the back
end, and you can hide that on the network, and put in a start up macro to
stop the file from being opened. Also, even if the do change it, they're
only modifying their own copy, not the one used by everyone else.

If you want to simplyfy the distribution of the front end you can use a
simple DOS batch file to copy the front end from the network to the user's
PC, and then launch the file. The user runs this batch file to start the
database and so always gets the latest copy of the front end. This also
means you don't need to worry about the front end bloating due to use use of
temporary tables etc as they will always get a fresh copy each time.
 
Back
Top