If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Database crash when adding new field and deleting the label
Hello,
Hoping somebody might have an answer to a problem I am experiencing with a database I "inherited" to maintain. I have several databases I work on, but this is the only one I have a problem with. In a nutshell, any time I add a field to any form or report and then delete the associated label, upon saving of the form/report, the database will "crash" (with the old "Microsoft Access has encountered a problem and needs to close") message and discard all of my changes since the last successful save. Sometimes it even completely trashes the form/report to an unuseable state and I have to recover the pieces of code and re-build the form or use a backup copy. As long as I save the form/report immediately after I add the field(s), but before I delete any labels, then this doesn't happen. A little history on this database: It was originally written in Access 97 (by me) and then taken over by somebody else for a number of years. Sometime during that era, they converted it access 2000. The problem never existed while in Access 97 to my knowledge, but when I resumed responsibility for it recently, that was one of the first things I noticed is that it seemed very unstable. Things I've tried to this point that have not worked: 1. development on a different machine to see if it was "computer specific" 2. repair/compact 3. Decompile/Recompile 4. importing all objects into a new database 5. Exporting form as text and re-importing 6. Converting database to a prior version (97) 7. Converting the database to Access 2003 Other things I noticed: 1. An old version of this program, still in Access 97, format does not have this problem 2. When I tried converting the database back to Access 97, just for curiosity, it completely failed. Begins to convert, but then aborts (no error) and I end up with an empty Access 97 shell (no objects). The only thing I've been able to get to work for a fix is to re-create it by manually copying all of the objects off of the form and pasting them into a new one and then copying/pasting all of the code, setting the datasources, etc. This seems to fix the problem, but I'm hoping there is a less time- consuming way of fixing this vs re-creating every form and report in this database. Sorry if this is a long, drawn out post, but I just wanted to provide as much detail as possible up front and avoid repeating steps I've already tried. Any input, suggestions, knowledge would be most appreciated. Thank you, Ryan -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...forms/201002/1 |
#2
|
|||
|
|||
Database crash when adding new field and deleting the label
Maybe this link will help:
http://www.access-programmers.co.uk/...ad.php?t=99179 Ryanspad1 wrote: Hello, Hoping somebody might have an answer to a problem I am experiencing with a database I "inherited" to maintain. I have several databases I work on, but this is the only one I have a problem with. In a nutshell, any time I add a field to any form or report and then delete the associated label, upon saving of the form/report, the database will "crash" (with the old "Microsoft Access has encountered a problem and needs to close") message and discard all of my changes since the last successful save. Sometimes it even completely trashes the form/report to an unuseable state and I have to recover the pieces of code and re-build the form or use a backup copy. As long as I save the form/report immediately after I add the field(s), but before I delete any labels, then this doesn't happen. A little history on this database: It was originally written in Access 97 (by me) and then taken over by somebody else for a number of years. Sometime during that era, they converted it access 2000. The problem never existed while in Access 97 to my knowledge, but when I resumed responsibility for it recently, that was one of the first things I noticed is that it seemed very unstable. Things I've tried to this point that have not worked: 1. development on a different machine to see if it was "computer specific" 2. repair/compact 3. Decompile/Recompile 4. importing all objects into a new database 5. Exporting form as text and re-importing 6. Converting database to a prior version (97) 7. Converting the database to Access 2003 Other things I noticed: 1. An old version of this program, still in Access 97, format does not have this problem 2. When I tried converting the database back to Access 97, just for curiosity, it completely failed. Begins to convert, but then aborts (no error) and I end up with an empty Access 97 shell (no objects). The only thing I've been able to get to work for a fix is to re-create it by manually copying all of the objects off of the form and pasting them into a new one and then copying/pasting all of the code, setting the datasources, etc. This seems to fix the problem, but I'm hoping there is a less time- consuming way of fixing this vs re-creating every form and report in this database. Sorry if this is a long, drawn out post, but I just wanted to provide as much detail as possible up front and avoid repeating steps I've already tried. Any input, suggestions, knowledge would be most appreciated. Thank you, Ryan -- RuralGuy (RG for short) aka Allan Bunch MS Access MVP - acXP WinXP Pro Please post back to this forum so all may benefit. Message posted via http://www.accessmonster.com |
Thread Tools | |
Display Modes | |
|
|