Deploying database

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

Guest

Hello -

I have a small application that 10 users will be using mainly to add records
(about 60 per day each). They will occasionally have to print reports.

If I put this on the server and put a copy on each person's desktop, will
this be sufficient? Should I separate it into backend/frontend? If I do
backend/frontend, do I just split the database and keep the front end in the
same folder as the backend and put a copy of the frontend on each user's
desktop?

On the contrary, if each user should have their own copy of the front end,
how do I connect that to the backend?

Should I split the database and then make an MDE out of the frontend?

Any help will be appreciated!
 
yes, split the db into FE and BE files. the backend db goes on the server,
in a folder that each user has full rights to. link the frontend db to the
backend on the server, turn the frontend into an MDE file (** but make sure
you keep the "master" frontend database as an MDB file, so you can make
design changes when necessary**), and put a copy of the MDE file on each
user's computer.

suggest you see
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.granite.ab.ca/access/performancefaq.htm
for some very useful information on splitting databases.

hth
 
Hi Tina -

Thanks so much for your response! When I put the copies of the MDE on each
user's computer, how do I link it to the backend?
 
Sandy said:
Hi Tina -

Thanks so much for your response! When I put the copies of the MDE on
each
user's computer, how do I link it to the backend?
Click to expand...
You link to the BE from your development mdb FE copy. You then covert into
an mde and distribute it (the links are preserved in the copies). Use UNC
paths when linking your tables, don't use drive letter mappings since
different users might have different mappings.

Keith.
www.keithwilby.com
 
Back
Top