[AccessD] Desperately Seeking!

> I have built a client server application using .adp front end and SQL
> Server back end.  Within the application itself I use unbound forms and
> retrieve records using ADO recordsets at run time.  The way I have
> initially deployed the application is to copy an instance of the .adp to
> each desktop and run it locally.  The problem has been that people keep
> overwriting each other's updates - and changes are not reflected fast
> enough.

===========I'm not sure what you mean -- must they update in some particular
order?

> I have a couple of different thoughts on how to tackle this - either
> ratchet down the ODBC refresh rate, or run a single, centralized copy of
> the .adp (which throws up some non-updateable warning every time it
> starts which I don't know how to suppress).  Of course, I acknowledge
> that I am a total newbie, and both of these options may be flawed.

===========How are you currently updating? I'm assuming you're using the
UpdateBatch method -- is it a manual process where the user determines when
to update?

Susan H.