Question on deploy of multiuser MDE files

[RBPM]

Good morning to the forum,

My question(s) are on deploying a MS Access 2002 application in a network environment. Here is the situation:

1) The application is split into two databases - data and program. All the tables "live" in the data database and all other objects (queries-forms-macros-reports) "live" in the program database.

2) The application was developed in Access 2002 but under a 2000 format. I have converted the db up to a 2002 db and compiled the VB code. Also had no problem creating the MDE file.

Question(s)

1) Am assuming that the data db can reside on the server. Can the program db also reside on the server (in s seperate directory) or does it need to be installed on each users PC local hard drive?

2) Can anyone point me to more reading about deploying multiuser applications in access? I am still kind of new to a multuser envrionment and need some help?

3) Is there such a thing as a "checklist" for what needs to be in place for a multi-user app?

Any and all direction and guidance would be appreciated.

Thanks

 

[psemianonymous]

I can't think of a checklist, sorry, because depending on how your database works, we can skip a TON of items on the checklist. Here's a quickie:

o Front-end placement: most of the time you'll have no problems leaving the database front-end (front-end=programs part) on the server, but there are exceptions to this. The biggest problems with this are performance and weird 'passive mode' errors. I don't worry about this--put it on the server and change the setup only if you have to.

o Performance: Check out Tony Toews' awesome FAQ about this. He covers it ALL, and I mean ALL:

http://www.granite.ab.ca/access/performancefaq.htm

o Backups: make sure your data is backed up every day, as Access databases corrupt (rarely, but it happens). Also the frontend corrupts on occasion too.

o Security: I wrote a FAQ, but it's too long for any human being to read. In short: I recommend you don't bother with security. Also, I think you're already deploying this, so it's a moot issue now--you're already done.

o Everything else I've forgotten: sorry.