
April 30th, 2001, 05:55 AM
|
|
Contributing User
|
|
Join Date: Dec 2002
Posts: 14,575
  
Time spent in forums: < 1 sec
Reputation Power: 22
|
|
|
<i><b>Originally posted by : Kieran (Kieran.Darcy@ronin.com)</b></i><br />Hi Bryan,<br />I have had the same problem, in fact it has been the bane of my existence for the last few months, and to make matters worse I have had to use old DBase IV (DBF) files! I have managed to solve this problem, but it works only some of the time.<br />This http://support.microsoft.com/support/kb/articles/Q175/8/01.asp is how Microsoft say you should solve the problem when using DBF files, I don't know if it would apply to MDB files or not but it's definately worth a look. I have followed all of the suggestions in this article and found that the one that seemed to do the trick most effectively was related to the guest user. Hope this helps.<br /><br /><br />------------<br />Bryan at 3/21/2001 1:34:10 PM<br /><br />Hi. I've been having some difficulty connecting to an access database that resides on a diffeent drive on the same file server than my web site on our intranet. I'm trying to do this dsn-less. Of course my web resides on c: and my databases reside on f:. When I give the connection string db_connection="Driver=MicrosoftAccessDriver(*.mdb);DBQ=F:database sdb1.mdb;, I get an error telling me that the file's not found. Of course it is there and if I copy it to my virtual web folders, and give it a server.mappath(/databases/db1.mdb), all goes great. Unfortunately, users need to be able to write back to the database and this is a problem because we cannot allow write access from the masses back to the web servers. Hence we use f: for our databases. Any connection string help you could provide would be very helpful.<br />
|