re-linking backend tables on startup

[Rachael]

Hi, how do I go about getting my front-end database to prompt for and link to a backend database on startup. What code is required? Where do I put it?

I am distributing my database and have a set installation and linking location at the moment for the backend (c:/Program Files). My fear is that those users that install the program in different folders/drives will upset the links to the backend. So I thought a startup prompt for the backend location might alleviate my problem.

Any other ideas welcomed.

Thankyou for all replies, they will be appreciated.

Rachael

 

[Robert Dunstan]

Hi Rachael,

Unless I'm misreading your post I can't quite see the point of having a split database on each user's pc i.e. front end and back end

Normally you would split a database in a multi user environment, the back end tables residing on a network server and the front end on each pc. You would link to the back end by either mapping to it or using UNC naming conventions i.e. \\ServerName\FolderName\BackEndFileName.mdb
Using the latter means the user pc doesn't have to have a mapped network drive to the back end

If on the other you database application is unique to each pc why not put you tables in same database as your forms, queries etc.

HTH
Rob

 

[Jack Cowley]

Here are two Knowledge Base articles that might prove helpful in your quest:

http://support.microsoft.com/support/kb/articles/Q209/8/62.ASP?LN=EN-US&SD=gn&FR=0&qry=q209862&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=ACC2000

http://support.microsoft.com/support/kb/articles/Q291/2/64.ASP?LN=EN-US&SD=gn&FR=0&qry=q291264&rnk=1&src=DHCS_MSPSS_gn_SRCH&SPR=ACC2000

 

[pcs]

rob,

just a thought...i always split the db even when it is a single user app. this makes it much easier to maintain the application, as you can update the program with any concern about the users data.

al

 

[Rachael]

Yes pcs, the reason for splitting is to allow upgrades of the design without disturbing the users data. Thanks Jack for your reply, I will have a look at these now.

Thanks Rachael

 

[pcs]

Rachael,
in addition to Jack's kb links if you have a copy of the solutions.mdb you can check the following:
Use Multiple databases.
Linking tables at startup.

i was replying to rob's post of:
---------------------------------------
I can't quite see the point of having a split database on each user's pc
---------------------------------------

hth,
al

 

[Robert Dunstan]

Hi guys,

Yeah pcs you're absolutely right, it's always a good idea to split a database regardless if it's for multi-user use or not.

What I was referring to was if the person using the database on a stand alone basis was the developer as well. Generally what I do when I'm developing a database is I don't split it until I'm ready to distribute it and then when it is split I use UNC as the path to the BE and ensure that each user pc has the appropriate permissions set up on the folder etc.

I humbly apologize for causing any confusion and am off now to lie down in a darkened room!!!

 

[pcs]

aw heck, rob...at least take a candle with you

al