Faking a UNC path for split databases

[Paul H]

I want to start putting my backends in a UNC path instead of a mapped
drive...

If a client wants the database on their existing mapped drive Q: then it is
easy for my to create a Q: drive on my network so that I can set up the
table links before I visit the customer. With UNC paths this preparation is
not possible, it seems.

So lets say that a database I am about to deliver will be placed on the
clients network at \\server01\share01. Is there a way to fake the existence
of "server01" on my network without actually changing the name of one of my
PCs to "server01"?

Paul

[chris.nebinger]

Why don't you just follow the code here:

http://www.mvps.org/access/tables/tbl0009.htm

Then, the first time your client opens up the database, he is prompted
to relink the tables to wherever he wants.
Chris Nebinger
Paul H wrote:

I want to start putting my backends in a UNC path instead of a mapped
drive...

If a client wants the database on their existing mapped drive Q: then it is
easy for my to create a Q: drive on my network so that I can set up the
table links before I visit the customer. With UNC paths this preparation is
not possible, it seems.

So lets say that a database I am about to deliver will be placed on the
clients network at \\server01\share01. Is there a way to fake the existence
of "server01" on my network without actually changing the name of one of my
PCs to "server01"?

Paul

[Willem]

Paul H schreef:

I want to start putting my backends in a UNC path instead of a mapped
drive...

If a client wants the database on their existing mapped drive Q: then it is
easy for my to create a Q: drive on my network so that I can set up the
table links before I visit the customer. With UNC paths this preparation is
not possible, it seems.

..
..
..

>
Paul

You probably considered this already but just in case: how about having
front-end and back-end relative to each other?
The FE "knows" the path to itself and from there could (re)build the
link to the BE by means of code refered to in this thread or elsewhere.

[Willem]

... further you might use an .ini file that holds the path to your BE.
In your own .ini file you set the BE-path as you have it on your PC and
your client can specify in his .ini file the path to where his BE
resides.

Once you start that road it also opens a perfect way to an easy
procedure to update the FE at clients site as is explained here:
http://www.granite.ab.ca/access/autofe.htm

By the way .... suppose you want to add a field to the BE ...
Updating (changing the structure of) the BE can be done using the
BackEndUpgrader, a tool that you can incorporate in your FE, have a
look at this site:
http://www.databaseadvisors.com under: downloads.
(To use this one you need to incorporate/copy the supplied code into
your FE, if you're in a hurry you can look for a tool called "DATA PRO"
from: http://www.ssw.com.au but there are other as well)

[Paul H]

"Willem" <as********@yahoo.comwrote in message
news:11**********************@b28g2000cwb.googlegr oups.com...

.. further you might use an .ini file that holds the path to your BE.
In your own .ini file you set the BE-path as you have it on your PC and
your client can specify in his .ini file the path to where his BE
resides.

Once you start that road it also opens a perfect way to an easy
procedure to update the FE at clients site as is explained here:
http://www.granite.ab.ca/access/autofe.htm

By the way .... suppose you want to add a field to the BE ...
Updating (changing the structure of) the BE can be done using the
BackEndUpgrader, a tool that you can incorporate in your FE, have a
look at this site:
http://www.databaseadvisors.com under: downloads.
(To use this one you need to incorporate/copy the supplied code into
your FE, if you're in a hurry you can look for a tool called "DATA PRO"
from: http://www.ssw.com.au but there are other as well)

Thanks Willem,

Great resources and some useful tools. That should keep me busy for a while.
I am sure there is a solution in there, I'll let you know how I get on.

:O)

Regards,

Paul