Access 2003 MDB Issue Revising Forms
First of, this app has a history. I'll spare the details but it started life as an Access 2010 project. Saved out of 2010 accdb as an 2003 MDB. Didn't really use any of the 2010 functionality just wanted to move to a newer, supported platform.
There is no going back to 2010, the project deadline in a couple days.
I resolved the reference issues and ran thru the application functions. All looked good.
The issues began when I tried to modify one of the forms in the app. I added a new field to the form. When I tried to save the form the entire app locked up and canceled. I got the 'Do you want to send this error to Microsoft' box.
I tried every technique I know to resolve application issues:
I have:
1. Decompile/Recompile
2, Compact Repair
3. Created an entirely new blank MDB and pulled the entire application into it.
4. Make sure there a no unresolved references.
I was eventually able to revise the screen I was working on. But not the problem on other screens I am trying to revise. In the middle of a form revision the app locks. From that point on the form I was working on cannot be opened in development mode or any mode for that matter.
In that case I have pulled in the original version of the screen from a backup MDB and redo steps 1- 4 above.
The issue has occurred multiple times now and my deadline is fast approaching.
I have:
Decompiled many times,
Compact Repair many times
Created an enitrely new blank MDB and pulled the entire application into it several times.
Resolved all references.
I realize going from 2010 to 2003 is an odd situation and likely not one that is very common but I was hoping that there might be some ideas in the EE community.
There is no going back to 2010, the project deadline in a couple days.
I resolved the reference issues and ran thru the application functions. All looked good.
The issues began when I tried to modify one of the forms in the app. I added a new field to the form. When I tried to save the form the entire app locked up and canceled. I got the 'Do you want to send this error to Microsoft' box.
I tried every technique I know to resolve application issues:
I have:
1. Decompile/Recompile
2, Compact Repair
3. Created an entirely new blank MDB and pulled the entire application into it.
4. Make sure there a no unresolved references.
I was eventually able to revise the screen I was working on. But not the problem on other screens I am trying to revise. In the middle of a form revision the app locks. From that point on the form I was working on cannot be opened in development mode or any mode for that matter.
In that case I have pulled in the original version of the screen from a backup MDB and redo steps 1- 4 above.
The issue has occurred multiple times now and my deadline is fast approaching.
I have:
Decompiled many times,
Compact Repair many times
Created an enitrely new blank MDB and pulled the entire application into it several times.
Resolved all references.
I realize going from 2010 to 2003 is an odd situation and likely not one that is very common but I was hoping that there might be some ideas in the EE community.
Make sure there are no compile errors. They can sometimes cause what looks like corruption.
Try opening the app in a different version of Access. If you are using A2010, then open it with A2003 or vice versa. Different versions of Access are more and less sensitive to "stuff" and sometimes simply opening the app in a different version can straighten out the bit that is off.
Try opening the app in a different version of Access. If you are using A2010, then open it with A2003 or vice versa. Different versions of Access are more and less sensitive to "stuff" and sometimes simply opening the app in a different version can straighten out the bit that is off.
ASKER
PatHartman:
No compile errors.
As far as opening in a different version of Access:
The app was originally created in Win 7 Pro, Access 2010.
Saved as an Access 2003 MDB
Now running on a Win XP Pro, Access 2003 machine.
Are you suggesting I move it back to the Win 7 machine, open the MDB in Access 2010, save it and then move it back to the XP machine and open it in 2003?
No compile errors.
As far as opening in a different version of Access:
The app was originally created in Win 7 Pro, Access 2010.
Saved as an Access 2003 MDB
Now running on a Win XP Pro, Access 2003 machine.
Are you suggesting I move it back to the Win 7 machine, open the MDB in Access 2010, save it and then move it back to the XP machine and open it in 2003?
Yes. take it to the Win 7 PC and open it with 2010. Make some small change. Then bring it back. I know it sounds strange but then corruption is strange and this has fixed corruption for me even when all the steps you've gone through haven't. It's liking kicking the database "upside the head".
Are you doing your development work on the XP/2003 machine, or on the Win7/2010 machine?
If you're on the 2010 machine, try moving to the 2003 machine and doing your final build/compile there. Also try creating the new database and such on the 2003 machine. I've had issues when saving out of 2010 to older formats.
If you're on the 2010 machine, try moving to the 2003 machine and doing your final build/compile there. Also try creating the new database and such on the 2003 machine. I've had issues when saving out of 2010 to older formats.
ASKER
Since moving from 2010 on WIn 7 machine, all development is being done on the Win XP 2003 machine.
ASKER
Tried moving MDB to Win 7/2010 machine, opening the MDB, making a small change and saving it back to the Win XP/2003 machine.
The from I am trying to work on is called 'frmProperty'
Same issue. I added one button at a time and saved the form for each one. I was able to add 3 buttons. When I added the 4 button and a new unbound textbox, the form save OK. But then when I tried to run it I got 'You cancelled the previous operation' on the form open command when another form tried to open it.
Now frmProperty is basically dead. Will not open in design mode, cannot be called in run mode.
The from I am trying to work on is called 'frmProperty'
Same issue. I added one button at a time and saved the form for each one. I was able to add 3 buttons. When I added the 4 button and a new unbound textbox, the form save OK. But then when I tried to run it I got 'You cancelled the previous operation' on the form open command when another form tried to open it.
Now frmProperty is basically dead. Will not open in design mode, cannot be called in run mode.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
PatHartman: Thanks.
Since time is a serious factor, while I was waiting for an EE response, I had created a new blank form and set the recordsource to the same as the old form. Then I copied all of the controls and backing code to the blank form as you suggested. I am in the process of adding my new controls but it seems to be going well so far. The new contols and functionality that I couldn't add to the original form has been added to this one. I'm not done yet but at least have some hope. Fingers crossed, I've spent way too much time on some simple form revisions.
I think your export/import is also a good and previously unknown to me option. I'm sure I'm going to run into this again. I'll try the export/import before I recreate the entire form.
Since time is a serious factor, while I was waiting for an EE response, I had created a new blank form and set the recordsource to the same as the old form. Then I copied all of the controls and backing code to the blank form as you suggested. I am in the process of adding my new controls but it seems to be going well so far. The new contols and functionality that I couldn't add to the original form has been added to this one. I'm not done yet but at least have some hope. Fingers crossed, I've spent way too much time on some simple form revisions.
I think your export/import is also a good and previously unknown to me option. I'm sure I'm going to run into this again. I'll try the export/import before I recreate the entire form.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Excellent Information and thanks for the advice and words of experience. Thanks to your informative and honest responses I am not completely SOL. Yes, I'm in a very tight spot but at least I have a plan of attack if I encounter this issue again, which I know from your experiences, I surely will.
One thing I did to be proactive is to just go ahead and use the cut and paste method to recreate any forms that I know I will definitely be changing. It was a pain but much quicker than encountering any issue as the deadline fast approaches.
Once again thanks to EE for the big help right when needed.
One thing I did to be proactive is to just go ahead and use the cut and paste method to recreate any forms that I know I will definitely be changing. It was a pain but much quicker than encountering any issue as the deadline fast approaches.
Once again thanks to EE for the big help right when needed.
my 2¢