independent path queries??

[Boon]

Hi,

Here is my situation.

I have 3 database files stored in a folder. There are queries that make
table, append between database. (ie. Click make table in database1 to make a
table in database2.)

Currently, these 3 databases are stored in my laptop at path -->
c:\documents\project\Customer\

I would like to be able to move the folder Customer (which contains 3
databases) to other place and still be able to do the work. For instance, I
want to move the folder Customer to D:\Backup\August\Customer. Ultimately, I
want to move this to other PCs as well.

The problem is in the make query, I specify the path as
c:\documents\project\Customer\. Thus, when I move to different path, the
query doesn't work.

How can I make the query independent of the path. Just look in the databases
in the same folder it resides, or in the subfolder in the same folder in
resides?


Thank you,
Boon

 

[Banana]

If you want it to work without the drive letter (e.g. mapped drive), you
could use something like this:

\\computername\sharedfolder\subfolder\database

This will work for any computers regardless whether one computer uses
that path as C: and other uses it as D:

 

[Boon]

I am sorry but I don't understand. The computer name is different from one
pc to another. Your solution would mean that a user needs to change this
path everytime?

The database is to be used locally.

 

[Banana]

Oh, I thought you wanted to run queries against same computer from
different computer.

That said, I have to ask why would you want to do this? Normally, we
usually split databases and fix a backend copy in a certain location
that's accessible by all other computers and every one would have their
own copy of front end copy which would use the data from the backend, so
there's no need to "synchronize" the data.

 

[Boon]

It is a standalone applications. I have 3 databases in the same folder. I
cannot have one due to 1. the size (more than 2 GB), and 2. the fact that it
needs to be in 3 databases.) Think of it like a shipment transaction
database, and a rating database.

Thanks,
Boon

 

[Banana]

Well, even if it had to be three databases due to size and logical
requirement, it shouldn't prevent a properly split front-end copy from
being able to link to all three back-ends' tables and use them as
accordingly as well doing queries between two databases.

But if you're deadset on this, the only option you have is to
dynamically re-write the SQL based on the path that's correct at the
runtime.