How can I tell if FE is corrupted? Error with JET utility.

[RCurtin]

The FE of my database has been crashing during the last week and there have been a few other problems. I got errors saying that the BE was an 'unrecognised format'. I remember getting a 'not a valid bookmark' error also.

Another odd thing that was happening - when I put breakpoints in my code it was not breaking and stepping through it. It was like they weren't there. I realise now that editing the code while it was in break mode may have caused problems.

I didn't realise these issues were signs of corruption (until I started reading up on the subject and searching this forum) so have no idea when it started or what could be corrupt.

I used the compact and repair facility and it seemed to work fine. I can open all the forms and reports. I also decompiled the FE and it hasn't crashed since but I don't know if the problem is completly solved. From what I've read the problem could get much worse if I don't deal with it now.

The reason that I think that there may still be a problem is teh fact that the JEt compact utility will not work. I just get an error saying 'Error compacting database' straight away.

Is there a way to tell if something is corrupt or am I worring unnecessarily?

 

[Vassago]

Also the Jet Utility has different versions, depending on which version of Access the database was built in. If you try to run the utility on a database version the utility is not designed for, it will give you errors from my experience.

 

[RCurtin]

Hi,
Thank you for your replies - I was working on another project elsewhere so I couldn't try your suggestions at the time. However I've had to revisit this problem again as there does seem to be corruption - have another thread about it
http://www.access-programmers.co.uk/forums/showthread.php?t=107579

Anyways I ran the JET utility on the FE - I hadn't given the workgroup file last time (it calls it the system file - didn't realise it meant the workgroup file). It ran without errors - does that mean nothing is corrupt now?
I also imported everything into a new DB first.

It seems to be working ok but would really appreciate any suggestions as to how to pinpoint where the problem was or how I can tell if anything is still corrupt. Could you post these in the other post please.

 

[ghudson]

I also imported everything into a new DB first.

That probably fixed your problem if your db was corrupt. A db will appear to be working even if one of the system tables is slightly corrupted [then one day, boom, the db is too corrupt to be opened or repaired]. Importing everything into a new db is the best way to fix a system table problem.

 

[RCurtin]

Thanks Ghudson - I'm hoping it is fixed for good!
(Thats prob too much to ask tho - going on what I've read..)