Invisible database

[Guest]

Had a corrupted database so replaced it - now when I go to Form
Properties/options I get a Database connection error > Server error: Unable
to retrieve the list of record sources from a database using the connection
string:

DRIVER={Microsoft Access Driver
(*.mdb)};DBQ=URL=BGJ/postjob.mdb;UID=********;PWD=********

The following error message comes from the database driver software; it may
appear in a different language depending on how the driver is configured.

I found a different database connection in the drop down list which does work and I have altered the form to connect to this it works OK but the new database is not shown in the FPDB file so where is it?

Help! Ray

 

[Andrew Murray]

Have you published it to the *correct* folder? FP likes to put all DB's in
the fpdb folder, but you can override that and put them whereever you like
as long as the connection string points to it correctly,

If you look closer at the connection string, this gives you the clue:

DRIVER={Microsoft Access Driver
(*.mdb)};DBQ=URL=BGJ/postjob.mdb;UID=********;PWD=********

If appears therefore, your database is actually (or should be) in a folder
called "BGJ", not "fpdb".

If the folder was 'fpdb' the connection string would be:

DRIVER={Microsoft Access Driver
(*.mdb)};DBQ=URL=fpdb/postjob.mdb;UID=********;PWD=********

(notice the difference in the DBQ=URL= bit).

 

[Thomas A. Rowe]

If you place the database in any folder other then the fpdb folder, you will have to have your web
host set permissions for access the database on the folder.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Andrew Murray]

OK...my advice was based on the fact that with my host at least, access
databases work outside the fpdb folder.

In any case the rest of my post stands; the connection string points to
"BGJ" not "fpdb", which I think is where the OP's problem lies.

 

[Guest]

Hi Andrew, Thomas,

Yep, I see that - I guess when I stored the corrupt database in bgj it took
with it the connection. But my problem remains - the new database "postjob2"
is now specified in the asp. form but seems to update an existing database:
"postjob" (which is in fpdb.) so although it all works I just wonder how and
why?

 

[Thomas A. Rowe]

When I bring a site live, the database is never stored within the web root, always outside the web
root., which is only accessible via a FTP application.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================