I need to split a database

[Francesca]

Hello where I work I need to split a database so that it can be worked on by
lots of people at the same time. I have tried out database splitter and it
all seems straightforward. Are thew any pitfalls that I am going to
encounter? How do I get the front end on each machine to see the back end?
(or does that happen automatically)

Could anyone just sketch out the steps (and possible pitfalls) in easy
language so that I can do it with the least possible disruption to
everybody's work.

As you can probably tell I'm not an IT employee, just someone who's more
willing to give it a go than anyone else in the office.

Thanks for your help.

 

[Joan Wild]

Splitting is fairly straightforward. However, since you asked this in the
security newsgroup, is the database secured? If so, using the database
splitter will result in a secure frontend and a completely unsecure backend.
For this reason you may wish to split the database manually. If it isn't
secured, then no problem.

When you run the wizard, it asks you for a location for the backend
(tables). Choose a location on the server that all users have modify
permissions (windows permissions) to. The copy of the frontend in the
resulting file will have links to this location. It is a good idea to use
Network Neighborhood to specify the location of the backend, so that UNC
path names are used.

All you need to do is copy the frontend you created to each workstation.
Since you are copying a file that contains the UNC links, the copy on the
destination computer will also - nothing further to do.

There are various methods you can use to automate the dissemination of
frontends, and changes to them, to workstations. Tony Toews has one
example.
Look for frontend updater on his site.
http://www.granite.ab.ca/accsmstr.htm

 

[Albert D. Kallal]

Check out:

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

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm