"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
