Controls and Records will NOT update

[dragongunner0351]

Hello All,
today something very strange happened to our DB, none of the records will update, the command buttons do not point were they are supposed to, if I click on a calendar control (example here) I get a cannot update error, I cannot select anything from any combo box controls because this is updating and as I just stated records are not updating, its as though the DB is locked. Last Friday all was well with the DB, today FUBAR! Aside from the error message about not being able to update, I am also getting Error '2046' SaveRecord is not available at this time. I have seen a few posts similar to Error 2046, however this problem seems to be affecting my DB across the board. I am currently running my DB on Windows Server 2003 SP2, Office 2003 with current updates and SP's, I am utterly lost and can not determine the root cause. If anyone has any suggestions I am all ears.

 

[maxhugen]

Do you have a separate frontend and backend? When no-one has the db open, do you have an ldb still? (if yes, try deleting the ldb file, and re-opening the db).

Max Hugen
Australia

 

[dragongunner0351]

Hello Max, thanks for the reply, yes I do have a fe and be, however when no one is in the DB the ldb deletes, currently no one is in and therefore there is no ldb. Any other suggestions?

 

[maxhugen]

Can you open the BE and edit a record in a table directly?

Max Hugen
Australia

 

[dragongunner0351]

Yes

 

[maxhugen]

Have you tried editing a record in a table via the FE?

Have you recently rolled out an updated version of the FE?

Max Hugen
Australia

 

[dragongunner0351]

No, I spoke with one of the users, he was inputing data then as he was saving the record he lost his network connection. He is on a laptop with a wireless connection. From what I have been able to figure is that the database is in some form of a locked state. What is strange is that on some portions of the subform I can manipulate the data, but other portions of the subform and form I can not.

 

[maxhugen]

It sounds like there may some corruption in the BE. Have you tried doing a Repair/Compact on the BE?

Max Hugen
Australia

 

[dragongunner0351]

Max, that was one of the first things I tried. I am about to lose my religion

 

[maxhugen]

He-he, "keep the faith". There's always an answer, though I've lost some hair during some very ugly probs in the past.

I'd try decompiling the FE, recompiling, then Repair/Compact.

Max Hugen
Australia

 

[dragongunner0351]

How exactly do I decompile the FE?

 

[dragongunner0351]

I found a webpage that describes how to decompile the frontend

 

[maxhugen]

If it's still not working after that, I'd copy the BE to your pc, connect the FE to this copy, and try again (just in case there's a network issue, though I don't think this is the problem).

Max Hugen
Australia

 

[dragongunner0351]

Hey there Max still no go after the decompile and I have been working with a local copy since the problem

 

[maxhugen]

Ok, what else can we think of?

What is strange is that on some portions of the subform I can manipulate the data, but other portions of the subform and form I can not.

Let's concentrate on the subform. You indicate that you can edit data in some fields, but not others. Is the subform based on one table?

 

[dragongunner0351]

Yes, the form -> orders table, subform -> order details table. I am thinking that when there was a momentary loss of a network connection that the DB was put into a locked state. When I initially began looking into this problem I began by going through the various tables looking for anything obvious. Well, the user at the time of the network connection loss, was inputting a new customer. In the customer table I had one row blank and the new customer entry was populated with #####'s in all fields.

 

[maxhugen]

Locking of an Access file is controlled by the ldb file. You mentioned before that when no-one was using the mdb, there was no ldb, which indicates that Access has released any locks.

I'm puzzled that you can edit some fields on the subform, but not others, considering its based on just one table...

Try opening the query for the subform, switch to datasheet view, and check that you can edit every field of one record...



Max Hugen
Australia

 

[dragongunner0351]

I was able to edit and manipulate every field in datasheet view.

 

[maxhugen]

OK, then the problem may be with the subform itself - possibly a corruption that wasn't fixed by previous steps.

Create a new subform - from scratch! - and try editing that. It can be just a rough 'n ready form, as we're just trying to isolate the cause of the problem.

Max Hugen
Australia

 

[dragongunner0351]

No problem, I'll give it a go and let you know.