Dear fellow access users,

Many thanks for all the assistance in the above threads. I can report a
very pleasing 'ok' on using the split procedure tool from within
access.  I will be using the AutoFE tool, which looks brilliant to
update the FE clients.

To reitirate here was my goal and the procedure used to get there :-

Goal :- To split access from one single system which loaded via a
public share. The requirment came apparent as this was a 'desktop'
system which had a very important access repository on it. If any
hard-disk or part of the system was to fail, only recovery from backup
was possible and then onto a machine which would have to be made
available. Alot of network traffic was also used in each desktop system
loading the entire application across the network.

This led to thought I should split the database onto our well specified
back end server (Dell PE2450 DualPIII900, mirrored C:\, RAID5+1 all
other data, automated backups onto dds3) and have the front end on each
client. This would also enable me to update the FE client without
having exclusive access to the database.

How accomplised :-

1) I first backed up the database from the system it was ! This was
multiplebackups, one tape,  3rd system hard-disk and remote system
backup. I knew then if it all went wrong I had a backup to recover to.

2) I created a new directory called 'Database' on the Raid5+1
filesystem, i named the share. 'Database'. I copied the current
database onto the new fileshare.

3) I unmounted the old fileshare from each CLIENT system and remounted
the new Database share in the same place.

4) I ran the database from the new share. I than the run the split
wizard, putting the back-end tables onto the share i.e.
mydatabase_be.mdb.

5) On the client system i created c:\DATABASE. I copied the front end
into this directory.

6) I created a directory on the backed system called 'DISTRIBUTE' this
contains the database to install on other machines, and will no doubt
come in use when running the auto-fe tool.

7) I went to each other front end system and created a C:\DATABASE
directory and copied the my_database front end from DISTRIBUTE. I
opened up each database in tern leaving it open and seeing that the
tables where linked.

8) (not essential step, but useful) I am lucky enough to be using a
Cisco switch with a Netra T1. I setup SPAN (Switch Port Analysis)  and
monitored the traffic going through the switch on the backend. I could
measure the amount of traffic used and the 100MbFDX we are using is
more than adequate for the clients we have, this will help ensure there
is no dataloss or corruption from the internal network.

9) I ran thru the database test procedure, i.e. testing the database
done what it was supposed and as it was before prior to the split.

10) I wrote this and had a beer :)

again many thanks for everyones help. I really like the newsnet
community and I hope that my work goes towards furthering the
generosity and application of those people who geninually wish to help
each other.

Regards,

Alan Knipmeyer