ADP in a multi user environment

[Jeff via AccessMonster.com]

Just wondering how an ADP is best setup in a multi-user environment.
Specifically, is it best to have each user with their own ADE front end on
their local machine? Also, what about requering data? From my understaning
ADP uses a snapshot of the records so if a user had a form open for the
entire day it would not reflect the current data unless he/she triggered an
event to requery the data. Is there a way to auto update this snapshot?
Thanks,

 

[Alex White MCDBA MCSE]

Hi Jeff,

Never share front-ends, always put them on the local computers or what is
the point of the client-server system with everything on the server,
converting the ADP to ADE will give some performance improvement based on
the fact the file is smaller after compilation. Yes the idea of snapshot is
true but this is true for most databases, if keeping the clients completely
up to date, this does not really apply in most instances because the only
time I can think of where it would really matter is if someone was sitting
in front of the same screen and it is say a list of jobs and they never move
off the screen, because closing that screen and re-opening it would refresh
the data, if you really do need this then look for the timer event for that
form and do something like me.lstJobs.Requery every 30 seconds, but then
your are increasing network traffic.

If you need more info post back here, more than happy to go into more
detail.

 

[Vadim Rapp]

Hello Jeff:
You wrote in conference microsoft.public.access.adp.sqlserver on Mon, 09
May 2005 16:01:13 GMT:

JvA> Just wondering how an ADP is best setup in a multi-user environment.
JvA> Specifically, is it best to have each user with their own ADE front
JvA> end on their local machine?

from the development/deployment standpoint it's better to have one copy on
the network share. But then you have to make it read-only (which I would
recommend even in case of a local copy, due to some bugs in Access).

Vadim Rapp