Runtime Deployment for a Split Database

Hi

Apologies if this has been covered before - I promised I have searched and not found an answer.

I have just purchased the Access Development Extensions so that I can deploy my database's to users without Access. So far, I've managed to create an intallation file fine. Hwever, the database is to be used by multiple people and needs to be split.

If I create the runtime application of the frontend, all of the tables point to the backend on "my computer". I then need to give it to my client who will store the backend on thier server. How do I then make the front end (all locked becuase it's runtime) point to the backend in the new location?

I hope that makes sense.

I'm supposed to be installing this tomorrow, so any help would be much appreciated

Thanks

I SUSSED IT!, as no one responded to my question I thought I'd tell you how I did it. Surely I'm not the only one who has this problem....or maybe I am.


I attached the backend of the database as an additional file when I packaged the database. Once the datbase was installed, I saved it to the server, and pointed the desktop shortcut to that location. I also put in some code (found from the microsoft website) which made sure that the front end linked to the back end tables. If the link isn't found it allows the user to browse for the backend location files.

The link to that article is http://support.microsoft.com/kb/154397/

Hope this helps!