fractalvibes
08-15-2003, 02:42 AM
Ok, now I have a question! We have an older ASP app written circa 2000. It uses Access - about 16 tables and around 25 Access queries. The mandate is to move all Access databases, image files, etc. to a machine separate from the Server(s) for load balancing purposes. So - have tried putting a table on a NAS
(Network Addressable Storage) machine and connecting to the table via something like this:
If MDB is located on a Network Share
oConn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
"Dbq=\\myServer\myShare\myPath\myDb.mdb;" & _
"Uid=admin;" & _
"Pwd="
We don't use Access anymore, and when we did, we always place the *.mdb in the same folder(or subfolder) as the app, so I am totally unfamiliar with how this might work. Using the above formula for the connect string simply does not work. Any advice appreciated!
We use DB2 normally, for our database these days, and the app will eventually be converted, but we need a quick fix with minimal
tinkering with the thing for now...
thanks,
FractalVibes
(Network Addressable Storage) machine and connecting to the table via something like this:
If MDB is located on a Network Share
oConn.Open "Driver={Microsoft Access Driver (*.mdb)};" & _
"Dbq=\\myServer\myShare\myPath\myDb.mdb;" & _
"Uid=admin;" & _
"Pwd="
We don't use Access anymore, and when we did, we always place the *.mdb in the same folder(or subfolder) as the app, so I am totally unfamiliar with how this might work. Using the above formula for the connect string simply does not work. Any advice appreciated!
We use DB2 normally, for our database these days, and the app will eventually be converted, but we need a quick fix with minimal
tinkering with the thing for now...
thanks,
FractalVibes