![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Hello, Just tried to create a new form on an a2k app running on win xp pro that I've been working on for months and instead of getting a blank default form I get pieces, subforms actually, of another form in the app and a warning that I'm out of memory. OS then asks me if I want to send an error report to ms and shuts down Access. If I delete the suspect form from the app I'm back to normal and can create a new form without error but since the bad form is complicated I'm reluctant to rebuild it from scratch. Even my earliest backup has the same problem so that won't help either. I've tried compact/repair, importing everything into a new db, deconsctucting the bad form a piece at time, deleting the module behind the form, pasting everything from the bad form to a new form--nothing works. Just to check my sanity I imported the bad form into a new db--just the bad form--and it crashed the new db also. Can anyone explain why this is happening and suggest how I can recover/repair the bad form? Thanks, Mike |
![]() |
| Thread Tools | |
| Display Modes | |
| |