The notorious Access "ldb" lock file...

[Isadore]

Question: On rare occassions I throw up an aspx page that isn't fully tested (inadvertent error) and next thing I know I've broken a connection to the database table due to an error.

This creates an "*.ldb" lock file which the Server will not allow me to delete; therefore, the entire web site is shut down and inoperative. We haven't released the site to clients yet but what happens when, say, the power goes out at Kim Lee's house in Hong Kong...will that produce an "*.ldb" file on the Server? Or is this wonderful feature limited to Administrators only? Any clues, ideas? There must be a solution to this...

 

[Isadore]

Its been a long nite. I got rid of it; here's how. I couldn't delete it directly off the Server so I ran one of the aspx pages on the web that used the locked mdb (with proven code) and after I ran it the ldb file disappeared. Not sure what triggered that -- still leaves me curious about the creation of an *.ldb when clients start hitting the site.

 

[link9]

For web applications, you really should consider moving to a more robust platform for storing and accessing your data. I know Access will work, but it is problematic.

You know that MS offers the MSDE engine for free? It's one of the best kept secrets that most ppl don't realize. You can use the full fledged SQLServer Enterprise Manager to administer it and everything.

SQLServer is definitely better, as MSDE technically isn't supposed to support more than 5 concurrent connections, but that's only the point (according to them) that performance will start to degrade. You're not going to get errors, though. You also don't get the fulltext search service that comes with SQLServer, but hey, you don't get that with Access, either.

Anyway... check it out.
paul