S
slough art
Guest
Hi
Any help much appreciated…
I have created a “data access page” using Access, so that I can display the content of a simple Access database online. When I test it locally it works.
This is the connection string:
Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data Source=\inetpub\wwwroot\access_Jan_06\dynamic.mdb;Mode=Share Deny None;Extended Properties="";Persist Security Info=False;Jet OLEDB:System database="";Jet OLEDB:Registry Path="";Jet OLEDBatabase Password="";Jet OLEDB:Engine Type=0;Jet OLEDBatabase Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;Jet OLEDBon't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False
The problems start when I try and use it with my hosting company, and their ODBC manager to “add a data source” I have the following questions…
1.
“what is the name that the script uses to connect to the source database?” Is it Admin? I can see “ID=Admin” above. Or is the name outside of the connection string?
2.
My hosting company specify that I have to use the “full path” in order to describe the location of my database file, does \inetpub\wwwroot\access_Jan_06\dynamic.mdb look okay? They use IIS
3.
Should I use the full path is describe the location of my database file in the connection string as well? In the example above I have, but surly dynamic.mdb is enough after all my database and my data access page are in the same directory, and if I use the full path I would have thought I also need some ..\..\ at the beginning of the URL..
Thanks
Any help much appreciated…
I have created a “data access page” using Access, so that I can display the content of a simple Access database online. When I test it locally it works.
This is the connection string:
Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data Source=\inetpub\wwwroot\access_Jan_06\dynamic.mdb;Mode=Share Deny None;Extended Properties="";Persist Security Info=False;Jet OLEDB:System database="";Jet OLEDB:Registry Path="";Jet OLEDBatabase Password="";Jet OLEDB:Engine Type=0;Jet OLEDBatabase Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;Jet OLEDBon't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False
The problems start when I try and use it with my hosting company, and their ODBC manager to “add a data source” I have the following questions…
1.
“what is the name that the script uses to connect to the source database?” Is it Admin? I can see “ID=Admin” above. Or is the name outside of the connection string?
2.
My hosting company specify that I have to use the “full path” in order to describe the location of my database file, does \inetpub\wwwroot\access_Jan_06\dynamic.mdb look okay? They use IIS
3.
Should I use the full path is describe the location of my database file in the connection string as well? In the example above I have, but surly dynamic.mdb is enough after all my database and my data access page are in the same directory, and if I use the full path I would have thought I also need some ..\..\ at the beginning of the URL..
Thanks