dbTalk Databases Forums  

A2010 woes

comp.databases.ms-access comp.databases.ms-access


Discuss A2010 woes in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
jbguernsey
 
Posts: n/a

Default A2010 woes - 08-26-2010 , 11:07 AM






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

Reply With Quote
  #2  
Old   
jbguernsey
 
Posts: n/a

Default Re: A2010 woes - 08-26-2010 , 11:09 AM






On Aug 26, 5:07*pm, jbguernsey <j... (AT) angelsystems (DOT) co.uk> wrote:
Quote:
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
Oops. Meant qry,
mod, mcr, rpt and frm - not qry,
mod, mcr, mod and frm

JB

Reply With Quote
  #3  
Old   
paii, Ron
 
Posts: n/a

Default Re: A2010 woes - 08-26-2010 , 01:54 PM



"jbguernsey" <jeff (AT) angelsystems (DOT) co.uk> wrote

Quote:
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.

Reply With Quote
  #4  
Old   
a a r o n _ k e m p f
 
Posts: n/a

Default Re: A2010 woes - 08-26-2010 , 01:57 PM



maybe you should use SQL Server, only retards use Jet as a database




On Aug 26, 9:07*am, jbguernsey <j... (AT) angelsystems (DOT) co.uk> wrote:
Quote:
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

Reply With Quote
  #5  
Old   
jbguernsey
 
Posts: n/a

Default Re: A2010 woes - 08-26-2010 , 03:54 PM



On Aug 26, 7:54*pm, "paii, Ron" <n... (AT) no (DOT) com> wrote:
Quote:
"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.
Ron,


Thank you for your interest. Database is split. The clue is in the
'started with re-linking' phrase.

Aaron Kempf ... change the record (pun intended)! How do you know the
back-end isn't SQLServer?

As far as retards are concerned ... you know the saying about takes
one to know ...

Play nicely!

JB

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.