Multiple user front-end advice

M

Max Yaffe

Several times I've seen the advice to have a database front-end
(forms, reports, code...) on user's machines and data table in a
back-end on the server.

It sounds nice but doesn't it cause a maintenance headache. What if
some part of the design changes. Is there an easy way to redeploy the
front-end?

Thanks,
Max
 
R

Rick B

Yes. do a search and you will find many posts on how to update your
front-end. I check a revision date in my front-end against a revision date
in my back-end (the highest) and if they are not equal, I run a batch fiel
to shut down the front-end and copy the new version from the LAN.

There are "auto-updater" tools out there that have been written by other
Access gurus.

http://groups-beta.google.com/groups?q=microsoft.public.access+"update+front+end"&qt_s=Search

Rick B
 
J

Jackie L

It is more of a maintenace headache if you do not split the data out because
the users would have to be kicked out in order to do any changes. This way,
they can continue to work and then the front end can be updated through a
..bat file. If you need help with that, please let us know.

Jackie
 
L

Larry Daugherty

Yes, it's a bit of a headache but not so much of a headache as not
doing it.

You are starting to see the next level. It entails a bit of thinking
and work but once done you'll be out on the golf course while those
who didn't bother are continually scrambling to maintain their
applications.

Look on Tony Toews's site for his FE Updater. It's a facility that
Tony has made freely available to everyone.

HTH
 
Top