how do i set up a database over two computers

hi everyone. i currently have a .mdb system built used as a reception system
on one PC and would like to use it over (at least) one more PC so that
multiple users could arrange appointments etc. if anyone could point me in
the right direction it be great. do i need to start again or can i move the
tables i have onto the server and use the .mdb i have as the front end. any
help will be greatly recieved

yours

david

David,

What you need to do is split the .mdb in a Front End (preferably an
..mde) which holds everything else but the tables, and a Back End which
holds only the tables, and store the back end on the server and a copy
of the front end on each PC's local HDD. Even though it may sound
somewhat scary right now, in fact the whole process is a walk in the
park! Just use Access's built-in splitting wizard:
Tools Database Utilities Database Splitter
in A2K, probably the same or something similar in later versions; not
sure if it exists in A97 if you're still there.
Two things to note: (a) before you do anything, make a backup copy
justin case, and (b) be prrepared with regard to the network folder in
which you will store the back end; while you can always move the BE
later, storing it in its final position during the splitting will save
you the trouble of having to re-link the tables in the front end.

HTH,
Nikos

DAVIDPEOVER wrote:
hi everyone. i currently have a .mdb system built used as a reception system
on one PC and would like to use it over (at least) one more PC so that
multiple users could arrange appointments etc. if anyone could point me in
the right direction it be great. do i need to start again or can i move the
tables i have onto the server and use the .mdb i have as the front end. any
help will be greatly recieved

yours

david

that great thanks. once ive done this will i be able to have two users using
the application to enter data without over writing each other? or do i need
to add locks to the forms.

"Nikos Yannacopoulos" wrote:

David,

What you need to do is split the .mdb in a Front End (preferably an
..mde) which holds everything else but the tables, and a Back End which
holds only the tables, and store the back end on the server and a copy
of the front end on each PC's local HDD. Even though it may sound
somewhat scary right now, in fact the whole process is a walk in the
park! Just use Access's built-in splitting wizard:
Tools Database Utilities Database Splitter
in A2K, probably the same or something similar in later versions; not
sure if it exists in A97 if you're still there.
Two things to note: (a) before you do anything, make a backup copy
justin case, and (b) be prrepared with regard to the network folder in
which you will store the back end; while you can always move the BE
later, storing it in its final position during the splitting will save
you the trouble of having to re-link the tables in the front end.

HTH,
Nikos

DAVIDPEOVER wrote:
hi everyone. i currently have a .mdb system built used as a reception system
on one PC and would like to use it over (at least) one more PC so that
multiple users could arrange appointments etc. if anyone could point me in
the right direction it be great. do i need to start again or can i move the
tables i have onto the server and use the .mdb i have as the front end. any
help will be greatly recieved

yours

david

David,

You will be able to hve many more than 2 users simultaneously, no
problem. You won't need to worry about locks, just leave Access's
defaults as they are; they will allow several users to work on the same
table (through forms), adding or editing records, they just won't be
able to edit the same record simultaneously; if they try, Access simply
won't allow the second one (recod level locking).

Nikos

DAVIDPEOVER wrote:
that great thanks. once ive done this will i be able to have two users using
the application to enter data without over writing each other? or do i need
to add locks to the forms.

"Nikos Yannacopoulos" wrote:


David,

What you need to do is split the .mdb in a Front End (preferably an
..mde) which holds everything else but the tables, and a Back End which
holds only the tables, and store the back end on the server and a copy
of the front end on each PC's local HDD. Even though it may sound
somewhat scary right now, in fact the whole process is a walk in the
park! Just use Access's built-in splitting wizard:
Tools Database Utilities Database Splitter
in A2K, probably the same or something similar in later versions; not
sure if it exists in A97 if you're still there.
Two things to note: (a) before you do anything, make a backup copy
justin case, and (b) be prrepared with regard to the network folder in
which you will store the back end; while you can always move the BE
later, storing it in its final position during the splitting will save
you the trouble of having to re-link the tables in the front end.

HTH,
Nikos

DAVIDPEOVER wrote:

hi everyone. i currently have a .mdb system built used as a reception system
on one PC and would like to use it over (at least) one more PC so that
multiple users could arrange appointments etc. if anyone could point me in
the right direction it be great. do i need to start again or can i move the
tables i have onto the server and use the .mdb i have as the front end. any
help will be greatly recieved

yours

david

that great thanks for your help hope to have new system up and running soon

"Nikos Yannacopoulos" wrote:

David,

You will be able to hve many more than 2 users simultaneously, no
problem. You won't need to worry about locks, just leave Access's
defaults as they are; they will allow several users to work on the same
table (through forms), adding or editing records, they just won't be
able to edit the same record simultaneously; if they try, Access simply
won't allow the second one (recod level locking).

Nikos

DAVIDPEOVER wrote:
that great thanks. once ive done this will i be able to have two users using
the application to enter data without over writing each other? or do i need
to add locks to the forms.

"Nikos Yannacopoulos" wrote:


David,

What you need to do is split the .mdb in a Front End (preferably an
..mde) which holds everything else but the tables, and a Back End which
holds only the tables, and store the back end on the server and a copy
of the front end on each PC's local HDD. Even though it may sound
somewhat scary right now, in fact the whole process is a walk in the
park! Just use Access's built-in splitting wizard:
Tools Database Utilities Database Splitter
in A2K, probably the same or something similar in later versions; not
sure if it exists in A97 if you're still there.
Two things to note: (a) before you do anything, make a backup copy
justin case, and (b) be prrepared with regard to the network folder in
which you will store the back end; while you can always move the BE
later, storing it in its final position during the splitting will save
you the trouble of having to re-link the tables in the front end.

HTH,
Nikos

DAVIDPEOVER wrote:

hi everyone. i currently have a .mdb system built used as a reception system
on one PC and would like to use it over (at least) one more PC so that
multiple users could arrange appointments etc. if anyone could point me in
the right direction it be great. do i need to start again or can i move the
tables i have onto the server and use the .mdb i have as the front end. any
help will be greatly recieved

yours

david