Multiusers over a network

[Jeremy Corson]

I have a call log that i have been designing for some time now and it is soon
to be used. My last problem is to have it setup on a server so that we all
can use it. My question is what is the best way of doing this. I have no idea
what the best way to do this is. What i was thinking is just put the database
on the serve and have us all just use it at once. Is that going to create any
problems? And suggesting/instructions would be great! Also is Replication
just for computers that arn't connected to the server such as laptops?

 

[tina]

comments inline.

I have a call log that i have been designing for some time now and it is soon
to be used. My last problem is to have it setup on a server so that we all
can use it. My question is what is the best way of doing this. I have no idea
what the best way to do this is. What i was thinking is just put the database
on the serve and have us all just use it at once.

no, no, don't do that.

Is that going to create any
problems?
YES!

And suggesting/instructions would be great!

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

hth

 

[Ray Cacciatore]

Split your database into a front end and a back end. There is a Splitter
wizard within Access that automates this step. It's in the Tools menu. This
will split your application into 2 MDB files. One MDB will have only the
tables(the backend), the other MDB file will have the rest (the front end).
Copy the front end on everyone's workstation, place the backend on a shared
folder. You may need to refresh the attachments on each workstation
(especially if some users are mapped differently to the shared folder) but
you can use the Linked table wizard to refresh this as well.

Warning:
Do not put the unsplit version on a shared drive and have everyone open it.
This guarantees a corrupted file (eventually).

Ray