Split Database on CD

[SueBK]

I've been asked to provide a copy of a database to an external client. The database is split, with the backend normally residing on the server and each user having a front end.

I'm assuming my client won't have the Access knowledge to relink the tables, so how do I link them to the backend, which will be on the CD, before I even burn the CD?

 

[Mr. B]

Assuming that you are sending this just for testing by the external client and that they do not intend to use it in a multi-user environment you can do the following:

Create a special folder on your C-drive. Put the back-end file in that folder. Link the front-end file to the back-end file in the special folder on your C-drive. Send your client the front-end and back-end files, instructing them to create a folder on their C-drive named the same as your special folder you just created on your C-drive. This will have the front-end already linked to the back-end file because the path is the same.

If they are going to be using your database in a multi-user environment, you can ask them to provide you with the full network path to a folder that they will create just for the back-end file. Then you create the exact same path on your network putting the back-end file in that folder and link the front-end to it before sending the client the database files.

 

[gemma-the-husky]

a standard way is to provide code in the startup form to check whether the tables are correctly linked to the active back end, and if not, relink the tables.

it's often easier to do this, then expect users to do it manually.

if it's a single user demo, you could just work with local tables, ratrher than a linked back end.

 

[SueBK]

I decided to burn the backend to a CD; link the front end to that copy; then burn both FE & BE to a 2nd CD. I guess if I had a re-writeable capability I could have burnt the BE, linked the FE, then added the FE to the same CD. I just put the backend copy in the file as a backup copy.
Dave, does the code run every time or just when the FE can't find the BE?

 

[gemma-the-husky]

it's up to you. you need to check the vaidity of the link each time, but you do not need to relink, if the tables are already correctly linked.

i cannot see the point of issuing the fe/be on separate disks. They cannot be used on those disks anyway.

you either need to ensure your users understand how to link tables for themselves, or automate the procedure so they do not need to do it manually

 

[SueBK]

Sorry, didn't explain very clearly.

I burnt the BE to Disk 1.
Linked my FE to the Disk 1 BE - now all my links say "D:\BE"
Then I burnt the BE and my newly linked FE to disk 2, which I handed over to the client. The FE on disk 2 looks for the BE on disk 2.
Disk 1 I threw in my hard-copy files as a back-up disk of the data as at a that point in time.

Of course, if the client's CD drive is a different letter to mine - it all falls in a heap. At this point, the client's rep just wanted a 'look see' and play. The database is our tool, but they like the concept so much they're considering adopting it for their internal processes. (And hopefully hiring a programmer to do it properly. I'm a bit of a duct-tape and WD40 programmer.)

At the end of the project they will get all our data and they can do whatever they want with the database.

 

[Catalina]

May be this is what you need:

http://www.peterssoftware.com/tlk.htm

Catalina

 

[gemma-the-husky]

the thing is you won't be able to use a database on a CD, because it is read only.