By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,234 Members | 1,823 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,234 IT Pros & Developers. It's quick & easy.

Problem - absolute path to linked tables

P: n/a
I hope someone can help with this.

I have a website using Access and ASP developed on my own PC (using PWS) and
hosted on a commercial site.

I decided that splitting the dbase up would be a good management tactic; it
si easy to link from the main database and it works fine - on my own
machine.

Trouble is when I upload to the commercial host, it takes with it the
ABSOLUTE path of the linked database -which of course is different on the
website machine. If it used relative refs it would be fine but....

Does anyone know how to overcome this?

John Lewis

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
"John Lewis" <jo**@cocreation.co.uk> wrote in message
news:bn**********@news6.svr.pol.co.uk...
I hope someone can help with this.

I have a website using Access and ASP developed on my own PC (using PWS) and hosted on a commercial site.

I decided that splitting the dbase up would be a good management tactic; it si easy to link from the main database and it works fine - on my own
machine.

Trouble is when I upload to the commercial host, it takes with it the
ABSOLUTE path of the linked database -which of course is different on the
website machine. If it used relative refs it would be fine but....

Does anyone know how to overcome this?

John Lewis

I don't understand. Normally, in this newsgroup, "splitting" an Access
database means making two parts to the database: the back end contains the
data (tables only) and the front end contains everything else (forms,
reports, modules, etc). This is to keep the user interface separate from
the data. However, if you have developed an ASP site - the ASP pages are
the user interface - or do you mean you have more than one interface to
access the same data?

It looks like more of a simple ASP question not really for this newsgroup -
but your answer could lie in specifying
Server.MapPath("MyDb.mdb")
rather than "C:\MyData\MyDb.mdb")

Fletcher
Nov 12 '05 #2

P: n/a
Thanks Flectcher; you are quite right, splitting does have a specific
meaning -my apologies for sloppy language.

What I should have said is that I am using linked tables as a means to,
errm, separate a single database into smaller chunks. This is for management
reasons - downloading a file of 10 MB is a drag!

I never refer to the path in ASP; the linking is transparent, entirely
inside Access.

So I'm still stuck for an answer.

John
"Fletcher Arnold" <fl****@home.com> wrote in message
news:bn**********@titan.btinternet.com...
"John Lewis" <jo**@cocreation.co.uk> wrote in message
news:bn**********@news6.svr.pol.co.uk...
I hope someone can help with this.

I have a website using Access and ASP developed on my own PC (using PWS) and
hosted on a commercial site.

I decided that splitting the dbase up would be a good management tactic;

it
si easy to link from the main database and it works fine - on my own
machine.

Trouble is when I upload to the commercial host, it takes with it the
ABSOLUTE path of the linked database -which of course is different on the website machine. If it used relative refs it would be fine but....

Does anyone know how to overcome this?

John Lewis

I don't understand. Normally, in this newsgroup, "splitting" an Access
database means making two parts to the database: the back end contains

the data (tables only) and the front end contains everything else (forms,
reports, modules, etc). This is to keep the user interface separate from
the data. However, if you have developed an ASP site - the ASP pages are
the user interface - or do you mean you have more than one interface to
access the same data?

It looks like more of a simple ASP question not really for this newsgroup - but your answer could lie in specifying
Server.MapPath("MyDb.mdb")
rather than "C:\MyData\MyDb.mdb")

Fletcher

Nov 12 '05 #3

P: n/a
"John Lewis" <jo**@cocreation.co.uk> wrote in message
news:bn**********@news6.svr.pol.co.uk...
Thanks Flectcher; you are quite right, splitting does have a specific
meaning -my apologies for sloppy language.

What I should have said is that I am using linked tables as a means to,
errm, separate a single database into smaller chunks. This is for management reasons - downloading a file of 10 MB is a drag!

I never refer to the path in ASP; the linking is transparent, entirely
inside Access.

So I'm still stuck for an answer.

John


Hi John
Sorry I'm still not clear. What do you mean 'linked tables'? You mean you
have several .mdb files each with a number of tables? Do you understand the
use of Server.MapPath? Perhaps you could, for the puposes of de-bugging,
change your code so it prints the connection string to your browser without
trying to connect.

Fletcher
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.