[AccessD] ODBC

Marty,

  Yes, what gustav said was true.  The main reason the change was made to
delete the LDB file was to speedup the initial login under certain scenarios
with Netware.  It also cleaned it up by getting rid of phantom users that
would be sometimes listed.

Jim.

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly
Sent: Wednesday, October 11, 2006 1:52 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] ODBC

I was talking about a NTFS file lock on the ldb file.
I had seen recent references to this on an MSDN blog, whether it is true
so I fiddled around with this and created a fake .ldb in notepad
with one entry and closed it, so all file locks on the ldb were dropped
It opened up the mdb in 97 with no complaints.
so I guess you are right.

http://blogs.msdn.com/larryosterman/archive/2006/02/17/534234.aspx

You could use this code to see if a file lock is in place to test if the 
condition occurs
http://vbnet.mvps.org/index.html?code/fileapi/createfile_inuse.htm




Gustav Brock wrote:

>Hi Marty
>
>This is not so. If the ldb file exists, it will simply be reused (if not
corrupted, of course).
>Access 1.x and 2.0 even left the ldb file on purpose for reuse.
>
>/gustav
>
>  
>
>>>>martyconnelly at shaw.ca 09-10-2006 21:27:43 >>>
>>>>        
>>>>
>
>One of the checks that MS applies to determine a corrupt mdb is on opening
the mdb if the .ldb file is there but has no file locks on it, then the
database is considered corrupt and needs to be "repaired". ..
>
>
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com