Splitting a database after distribution

[Guest]

I created a data collection database that has been distributed to remote
offices on rented PCs. The PC's have Access 2K. I built and maintain the db
on Access 2002 but saved it in 2000 format. I want to split the databases in
the remote offices so I can replace the front-end instead of importing forms,
reports, etc for each enhancement.

I know P**7 but with deadlines and learning you go into production with the
database you have.

Problem: most of the rented PCs do not have the database splitter wizard
installed. When I try to urn the splitter I get a message about installing
that component from the CD which I of course don't have.

Question: Which option should I take:
a) Get a Office 2K CD and install the components (do I need a Windows 2K CD
also?).
b) Take my laptop and USB drive to each office, copy database to there, do
the split and then copy back to the remote PC.
c) Something else, no vague answers please (-8

Many thanks, Allen

 

[Douglas J. Steele]

One approach would simply be to provide a new front-end that links to the
existing database. Yes, you'd have a lot of unnecessary overhead in the
existing database (the queries, forms, reports, etc. that are no longer
used), but you could clean that up later.

 

[Guest]

Great idea, many thanks Douglas.

One approach would simply be to provide a new front-end that links to the
existing database. Yes, you'd have a lot of unnecessary overhead in the
existing database (the queries, forms, reports, etc. that are no longer
used), but you could clean that up later.

 

[Guest]

It appears that the Linked Table Manager wizard in Access 2000 is also not
installed on some of these machine. The work around I am using is the create
a directory path on my development machine that matches the production
machines. As the final step prior to rollout I put the front end database in
the that folder and use the Linked Table Manager to link to tables in the
same folder. I then backup that front end and go to the production machine
and install it.

Any better ways (without an autoexec macro invoked a function to
programatically reconnect tables)?

Many thanks, Allen.