SPLITTING

[Ransom]

Hi there.....
I've finally gotten the database together and I attempted to have it shared
between two users....however I was reading about splitting the
database....can anyone give me some concrete instructions about how to make
this work effectively.

I have three people who need to access the database that's all. However I
know it's possible that two people will be in it at the same time, entering
information?

Any suggestions?

Thanks
Ransom

 

[Kevin3NF]

Check out the wizard in Tools>>Database utilities>>Database Splitter (Access
2003)

Very straightforward and low risk. Put the Backend on a file share and a
copy of the front end on each workstation.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

 

[John W. Vinson]

Hi there.....
I've finally gotten the database together and I attempted to have it shared
between two users....however I was reading about splitting the
database....can anyone give me some concrete instructions about how to make
this work effectively.
http://www.granite.ab.ca/access/splitapp.htm

I have three people who need to access the database that's all. However I
know it's possible that two people will be in it at the same time, entering
information?

The official limit is 255 people. In practice, 40 or 50 works well with a
properly designed database (for entering data, not for changing design, which
requires exclusive access). Three users is NO problem.

John W. Vinson [MVP]

 

[Ransom]

OK...and forgive my novice skills...but which would serve as the "master" the
back end one I created or the one I used to split the database from?? Cause I
split it and created the file with the "be" extension on the shared drive and
the original file is still on my drive....I'd like to keep everything the
same, the form, the reports everything but I just want them to be able to be
in the system at the same time???

Thanks
ransom

 

[Kevin3NF]

back-end goes on the share, a COPY of the front-end (with all the forms,
reports, etc) goes no each users desktop in a properly split environment.

You CAN put the FE on the share as well and give each user a shortcut to
it...but if one user changes/deletes and object or the file itself, everyone
is hosed. Performance can be an issue as well.

--

Kevin3NF
SQL Server dude

You want fries with that?
http://kevin3nf.blogspot.com/

I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.

 

[John W. Vinson]

back-end goes on the share, a COPY of the front-end (with all the forms,
reports, etc) goes no each users desktop in a properly split environment.

You CAN put the FE on the share as well and give each user a shortcut to
it...but if one user changes/deletes and object or the file itself, everyone
is hosed. Performance can be an issue as well.

An alternative which one of my clients uses is to have the backend on a
server, and MULTIPLE frontends also on the server. Each user has their own
private directory with a copy of the frontend (which can be individually
customized if you want to take the effort). The users use CITRIX (or you could
use Windows Terminal Server) to connect to their own frontend.

Multiple users sharing the same frontend runs a high risk for trouble -
performance, corruption, contention for temporary tables (if you use them),
bloating to name a few.

John W. Vinson [MVP]