Recover a seemingly corrupted form

[GraeagleBill]

I've managed to find myself with a seemingly corrupted form. I had just added a label control and added code to set the caption in the Open code. Something in that process apparently corrupted the form. I can't open the form either in View or Design. I tried to recover by creating a new DB and importing "everything" but I get the same error again, even during the import process.






Anyone know how to recover from this?

Thanks,
Bill

[Bob Fitz]

Can you post a copy of the db

[NoellaG]

Hi,
some things you can try:
* if you still can open the database file, try to open the VBA window (ALT F11 or something like it) and then remove the code you added from the form. Then try to open the form again.
* try compact and repair
* remove the form from the database and import a copy from the last working back-up, then add the label again
* look at the size of your database file: has it blown up to nearly 2 GIGA for some reason?

[GraeagleBill]

App is in its infancy. Front-end and back-end MDB's plus a small token image file have been zipped. You'll need to un-zip into c:\CompList in order for the back-end table links to function properly. To trigger the 2004, simply double-click any one of the companies in the Record-Selection bar. In Debug, you will see the DoCmd.OpenForm that is attempting to open the offending form.

There was a ton of work done upon the previous functioning copy of the form. Mostly moving controls around, adding a few, resizing a few, deleting a couple, etc.

BillCompList.zip

[GraeagleBill]

Thanks for the thoughts. I tried all of what you suggested before initial posting.
Bill

[burrina]

Sometimes this happens when you run a action query on a large table. I did not download your db.
Try DeCompiling your db and then Debug your code.

HTH

[GraeagleBill]

Burrina, while I doubt that the problem is in the code, but rather with corrupted TB controls, I'm inclined to follow your suggestion. Funny, in all these years, I've never had an occasion to DE-compile.........how does one do that?

[Bob Fitz]

Burrina, while I doubt that the problem is in the code, but rather with corrupted TB controls, I'm inclined to follow your suggestion. Funny, in all these years, I've never had an occasion to DE-compile.........how does one do that?

The following link may help: http://www.fmsinc.com/microsoftacces.../decompile.asp

[GraeagleBill]

De-compile didn't clear up the issue. Sort of offers some evidence that the issue isn't code but rather corrupted controls.

[burrina]

Here is an example:

"C:\Program Files\Microsoft Office\Office\MSACESS.EXE" "C:\users\tim\documents\Mydatabase.mdb" /decompile

HTH

[ssanfu]

@GraeagleBill

I tried recovering your dB. No luck. Too many things are bad.

1) The major thing that is corrupt is the Autoxec macro.

2) The VBA project is also corrupt:
* the code for the Report - even though there is no code
* the code for the form "Record_Details"
* code for the form "CompList" is a little corrupt - but will get worse.


If you want:

In the IDE, copy the code from the form "Record_Details" & save in a text file.
Delete the Autoexec macro
Delete the form "Record_Details"
In the IDE, copy the code from the form "CompList" & save in a text file.
Open each of the standard modules and copy the code, saving to text files.

You have to copy - not export - the code because the VBA project is corrupt. If you just import them to a new databse, you will import the corruption also.

Now that the code has been copied, open the form "CompList" in design view, open the properties dialog box, click on the OTHER tab and set the property "Has Module" to NO. Save and close.

Create a new ACCDB. Set the options: Overlapping windows, un-check the autocorrupt settings, ensure the "Always use event procedures" is checked".

Import the tables, queries and the form "CompList". Compact and Repair. Save

Open the VBA IDE. Insert a Module. Rename the module and paste in the appropiate code. Compile the code and save.
Continue until all of the standard modules are entered.

Open the form "CompList" in design view. Add an event (say the OnOpen event) . In the IDE, delete the just added procedure and paste in the correct code from the text file. Compile the code. Close the IDE.
Compact & repair from the main window.

You will need to recreate the report and the form "Report_Details"... but you have the code.


Marking the "Has module" keeps the corrupted VBA from transferring to the new dB.

I learned this after 2 weeks of trying to recover from corruption.

IMPORTANT: DO NOT edit code while code is executing!!! Compile and save often.

3 rules of computing:
1)Backup!
2)Backup!
3)Backup!


(sorry about writing a book....)

[Missinglinq]

I couldn't even get to the IDE for the Record Details form. But, on top of your other problems, when I ran the CompList form and Double-Clicked on it, it broke on the Form_DblClick event. I went into the code for this Form and it was highlighting this line:

DoCmd.OpenForm frm, , , , , , "[LASTNAME]=""" & [LastName] & """" 'Yields an empty form

From the syntax, I'm assuming that

"[LASTNAME]=""" & [LastName] & """"

is supposed to be the criteria for the WhereCondition. The problem, here, is that you have it placed in the position for the OpenArgs parameter. To be used in the WhereCondition it should be

DoCmd.OpenForm frm, , , "[LASTNAME]=""" & [LastName] & """" 'Yields an empty form

Linq ;0)>

[GraeagleBill]

Long day, but the dust has settled. The big mistake was to have attempted to perform open-heart surgery on an old app in creating a substantially different app. I'll not waste your time elaborating. The corruption was so extensive that I had to essentially re-create the Record_Details form almost from scratch. And, while I doubt anyone will want to spend any more time on this, I'm posting another zip file with where I ended up. Thanks to all that gave their attention to this caper. Clearly, both Ssanfu and Missinglinq spotted the Remanents from the original app that were both troublesome and unwanted.

[Missinglinq]

Just glad that you got it working!

Linq ;0)>