![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
For info only. A few weeks ago I encountered a problem with A2010 which I put down to Auto Updates in Windows (XP SP3). *Re-installing A2010 didn't solve the problem but re-installing Windows did (thankfully, I got away without having to reformat ...) Now I have had a different problem, different client. *Database works OK but closing, whether from code on button or using the red 'x' just closes the database but leaves A2010 running. *Starting a different database in the same session just meant that database suffered from the same problem - Access wouldn't close. *Ctrl Alt and Del is the only way to close Access (only one copy appears to be running). *It may be that the DB is still lurking in memory somehow, don't know. Taking a copy home established that the problem was in the front-end. Other accdb's on the system are OK. Tried Repair & Compact. *No change. *Tried Decompile. No change. Imported all objects (in one go) into a new DB (actually accdb) - same problem. Removed objects from a decompiled copy one type at a time and imported objects from another decompiled copy (started with re-linking) qry, mod, mcr, mod and frm - testing after each import. *All successful. DB is now restored (with exactly the same objects as the 'faulty' one) and appears OK. Client had a power cut a few weeks ago and I had to remove some corrupted rows from a table (fortunately it was stuff from several years ago and didn't need replacing from old backups). *Problem only appeared after this. I assume some kind of corruption in the accdb file which was 'left behind' somehow when I imported objects by type ... JB |
#3
| |||
| |||
|
|
For info only. A few weeks ago I encountered a problem with A2010 which I put down to Auto Updates in Windows (XP SP3). Re-installing A2010 didn't solve the problem but re-installing Windows did (thankfully, I got away without having to reformat ...) Now I have had a different problem, different client. Database works OK but closing, whether from code on button or using the red 'x' just closes the database but leaves A2010 running. Starting a different database in the same session just meant that database suffered from the same problem - Access wouldn't close. Ctrl Alt and Del is the only way to close Access (only one copy appears to be running). It may be that the DB is still lurking in memory somehow, don't know. Taking a copy home established that the problem was in the front-end. Other accdb's on the system are OK. Tried Repair & Compact. No change. Tried Decompile. No change. Imported all objects (in one go) into a new DB (actually accdb) - same problem. Removed objects from a decompiled copy one type at a time and imported objects from another decompiled copy (started with re-linking) qry, mod, mcr, mod and frm - testing after each import. All successful. DB is now restored (with exactly the same objects as the 'faulty' one) and appears OK. Client had a power cut a few weeks ago and I had to remove some corrupted rows from a table (fortunately it was stuff from several years ago and didn't need replacing from old backups). Problem only appeared after this. I assume some kind of corruption in the accdb file which was 'left behind' somehow when I imported objects by type ... JB |
#4
| |||
| |||
|
|
For info only. A few weeks ago I encountered a problem with A2010 which I put down to Auto Updates in Windows (XP SP3). *Re-installing A2010 didn't solve the problem but re-installing Windows did (thankfully, I got away without having to reformat ...) Now I have had a different problem, different client. *Database works OK but closing, whether from code on button or using the red 'x' just closes the database but leaves A2010 running. *Starting a different database in the same session just meant that database suffered from the same problem - Access wouldn't close. *Ctrl Alt and Del is the only way to close Access (only one copy appears to be running). *It may be that the DB is still lurking in memory somehow, don't know. Taking a copy home established that the problem was in the front-end. Other accdb's on the system are OK. Tried Repair & Compact. *No change. *Tried Decompile. No change. Imported all objects (in one go) into a new DB (actually accdb) - same problem. Removed objects from a decompiled copy one type at a time and imported objects from another decompiled copy (started with re-linking) qry, mod, mcr, mod and frm - testing after each import. *All successful. DB is now restored (with exactly the same objects as the 'faulty' one) and appears OK. Client had a power cut a few weeks ago and I had to remove some corrupted rows from a table (fortunately it was stuff from several years ago and didn't need replacing from old backups). *Problem only appeared after this. I assume some kind of corruption in the accdb file which was 'left behind' somehow when I imported objects by type ... JB |
#5
| |||
| |||
|
|
"jbguernsey" <j... (AT) angelsystems (DOT) co.uk> wrote in message news:2016b883-7b01-4021-8434-1584ca952855 (AT) g17g2000yqe (DOT) googlegroups.com... For info only. A few weeks ago I encountered a problem with A2010 which I put down to Auto Updates in Windows (XP SP3). *Re-installing A2010 didn't solve the problem but re-installing Windows did (thankfully, I got away without having to reformat ...) Now I have had a different problem, different client. *Database works OK but closing, whether from code on button or using the red 'x' just closes the database but leaves A2010 running. *Starting a different database in the same session just meant that database suffered from the same problem - Access wouldn't close. *Ctrl Alt and Del is the only way to close Access (only one copy appears to be running). *It may be that the DB is still lurking in memory somehow, don't know. Taking a copy home established that the problem was in the front-end. Other accdb's on the system are OK. Tried Repair & Compact. *No change. *Tried Decompile. No change. Imported all objects (in one go) into a new DB (actually accdb) - same problem. Removed objects from a decompiled copy one type at a time and imported objects from another decompiled copy (started with re-linking) qry, mod, mcr, mod and frm - testing after each import. *All successful. DB is now restored (with exactly the same objects as the 'faulty' one) and appears OK. Client had a power cut a few weeks ago and I had to remove some corrupted rows from a table (fortunately it was stuff from several years ago and didn't need replacing from old backups). *Problem only appeared after this. I assume some kind of corruption in the accdb file which was 'left behind' somehow when I imported objects by type ... JB You may want to split the database into a Front end and Back end. You can then replace the front end with a copy if it get corrupted. |
![]() |
| Thread Tools | |
| Display Modes | |
| |