asp using a microsoft db...problems with .ldb file

[dnstapes]

I have several ASP pages that connect to an Access 97 database. I've found that if,
for whatever reason, my database crashes, the .ldb file will still show me as being logged on, even though I'm not. I've tried to delete the .ldb file, and I couldn't. I've gone into the server resources, and deleted all instances of someone using the database, and the .ldb still wouldn't let me delete it. The only thing I've found that works is rebooting the machine. But since this file is on a server that is being used by up to 100 people at one time, rebooting the server isn't always the best thing to do. To further complicate issues, if after the database crashed, and there remains an entry in the .ldb file, and someone tries to access one of the ASP pages, it causes a reaction that eventually shuts down all web serving for the entire server. This, as you can see, is extremely bad, and needs to be fixed.

At first glance, I think it'd be nice to have some way of being able to clear an .ldb file without rebooting (just deleting it is NOT an option, it doesn't work). Are there any programs out there that will let you clear the file? I've found some .ldb file programs types on Microsoft's web page, but I haven't found one that allows me to clear an .ldb file.

Any other possible suggestions on how to resolve this problem?

Thanks,
Dana

 

[Deadline]

The best solution for this issue is, DO NOT, I repeat DO NOT use a production server for you development purposes. Somehow, your employer has to afford a development machine. I have some real bad experiences in not doing so.

Thank you...
RR

 

[link9]

If you're running an application that might have 100 people using it, then Access is not going to be your best bet. It can't handle this amount of people, and it will get itself confused quite often.

The best solution to this problem would be to upgrade your database to something else, perhaps SQL Server, but mySQL would work, too (and it's free).

good luck

 

[dnstapes]

Just to clarify,

I do develop on a production server.

The server may have 100 people on it, not the database. The database generally doesn't have more than three users at one time, and that many is pretty rare.

Any other ideas?

 

[krappleby025]

hi their, i have the same problem, the reason is due to a fault in the scripting that causes the database and asp script to play against each other,

what i do is normally leave it for a while, (basically until the script time out occurs) which then clears the file from the system, on my computer it is set at 2.5 minutes......

Try that it may work, just leave the file for a while and then try it, it should work, it does for me,

 

[dnstapes]

thanks, how do you set the script time out?

 

[dnstapes]

Here's an update on my situation.

I decided to try the webpages out on a different server. I made copies of everything: the database and all related webpages. I made new odbc connections to the database, and re-established the links in UltraDev. All of a sudden, the webpages worked fine. When accessed through a web browser, no .ldb file was created.

I figured this might have something to do with the fact that I made new links to the database, so I refreshed the links on the first server. This produced some strange results. The home asp webpage would load up. This page has two recordsets to the database, one of the recordsets produces a list of links. When I clicked on one of the links, the web browser would hang on trying to load. Also, this time when I clicked the link, an .ldb file was created that had 17 connections to the database, all from the server. There are about 17 recordsets on the asp page that is trying to load up, so I think that's where that number comes from. But the page will not load. As of this writing, it has been trying to load for something on the order of a half hour. No error message has been returned to the browser, it's just sitting there trying to load.

Unfortunately, it's not an option to leave the asp pages on the server where they work. Even if it was, I'd still like to know what's causing this problem. What really gets to me is that the files that work on one server are identical to the files that don't work on the other server, everything is the same. This leads me to believe that there might be problems with IIS on one of the servers, but I'm not sure how to test that theory.

Any ideas? I'd really like to figure this one out.

Thanks,
Dana

 

[dnstapes]

Has anyone here heard of any problems with any versions of ASP? I just checked, and the server that has the webpages that doesn't work has a newer version of ASP than the server that has the webpages that do work.

Does anyone have ANY ideas for me?

Thanks