Databases Crashing - Any Ideas?

[Wayne]

My computer is dual boot Vista and XP. I have Access 2003 and 2007
installed on both partitions. The problem that I am having is that
some of my Access 2003 databases crash when I try to do a compact and
repair or create an .mde when using Access 2003 under Vista. I get
the classic "Microsoft Access has stopped working" dialogue. These
databases will compact and repair OK using A2007.

These same databases don't give any problems if I'm running Access
2003 under XP. The problem is only occurring when using A2003 under
Vista and only with specific databases. I've tried reinstalling A2003
but there is no change.

I realise that the reason is probably fairly obscure, but can anyone
have a stab at what might be going on here. I can't put my finger on
anything that is common to the databases that are giving the problem
compared to the databases that aren't.

[Bruce]

On Apr 14, 4:50 pm, Wayne <[e-mail]:

My computer is dual boot Vista and XP. I have Access 2003 and 2007
installed on both partitions. The problem that I am having is that
some of my Access 2003 databases crash when I try to do a compact and
repair or create an .mde when using Access 2003 under Vista. I get
the classic "Microsoft Access has stopped working" dialogue. These
databases will compact and repair OK using A2007.

These same databases don't give any problems if I'm running Access
2003 under XP. The problem is only occurring when using A2003 under
Vista and only with specific databases. I've tried reinstalling A2003
but there is no change.

I realise that the reason is probably fairly obscure, but can anyone
have a stab at what might be going on here. I can't put my finger on
anything that is common to the databases that are giving the problem
compared to the databases that aren't.

Sounds like you need the Access 2003 post SP-3 hotfix described below:

http://support.microsoft.com/kb/937560/en-us

Bruce

[Wayne]

Thanks for the reply Bruce, but I've refrained from installing SP3
after my last reformat. I've read a few posts that seem to indicate
that it breaks more than it fixes. The fact that it needed a hotfix
wasn't a good sign. :-)

[Wayne]

This is really weird. I've just done a bit more experimentation with
the offending databases. If I do a simple file copy of the frontend
file that is causing the problem, the copied file will compact and
repair and also compile to an mde no problems. Yet the original file
won't. Go figure.

[Bruce]

On Apr 17, 3:48 am, Wayne <[e-mail]:

This is really weird. I've just done a bit more experimentation with
the offending databases. If I do a simple file copy of the frontend
file that is causing the problem, the copied file will compact and
repair and also compile to an mde no problems. Yet the original file
won't. Go figure.

The aforementioned hotfix does not appear to need SP3, at least it
wasn't mentioned as a prerequisite in the knowledgebase article.
Perhaps they named it 'post-SP3' just to indicate that it was not
included in SP3. That the repair and compact works on a direct copy
but not the original is mysterious indeed. Perhaps it's a permissions
issue on the folder where you're making the copy?

Bruce

[Vish.Dwi]

Unrecognized file format error comes when you use later database file
on higher version file. To get rid from this problem you have to
convert you should open your file in same version in which it created
now from tool menu you convert your database to higher version. And
save your file. In this you can repair your database file. If any case
you couldn’t repair your database through this way then you should try
some access recovery software like Stellar Phoenix Access Repair
Software.
Download Link: Http://www.repair-access-file.com

[Linq Adams via AccessMonster.com]

>The aforementioned hotfix does not appear to need SP3, at least it

>wasn't mentioned as a prerequisite in the knowledgebase article.
Perhaps they named it 'post-SP3' just to indicate that it was not
included in SP3.

I suspect MS figured even the slowest user would understand that you only
need a hotfix for a given service pack if you have that service pack
installed! The hotfix is not for things not included in SP3, but to ***fix***
things in SP3! Hence the name hotFIX.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200805/1

[Bruce]

On May 8, 7:01 am, "Linq Adams via AccessMonster.com" <u28780@uwe>
wrote:

The aforementioned hotfix does not appear to need SP3, at least it
wasn't mentioned as a prerequisite in the knowledgebase article.
Perhaps they named it 'post-SP3' just to indicate that it was not
included in SP3.

I suspect MS figured even the slowest user would understand that you only
need a hotfix for a given service pack if you have that service pack
installed! The hotfix is not for things not included in SP3, but to ***fix***
things in SP3! Hence the name hotFIX.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via AccessMonster.comhttp://www.accessmonster.com/Uwe/Forums.aspx/databases-ms-access/2008...

I understand that your post is simply meant to enlighten the readers
of this newsgroup and not merely to belittle someone that you think is
stupid and this is commendable. However, one must wonder why
Microsoft explicitly indicates that certain SP levels must be
installed for some of their post-SP hotfixes and does not so indicate
for others. Indeed there are many post-SP Access hotfixes which are
supported without having the indicated SP itself installed or which
simply require the previous level SP installed, i.e. there are post-
SP2 hotfixes which require only SP1. You may well be correct in this
particular instance since Microsoft does not explicitly state that SP3
is not required. However, to state or imply that all hotfixes for a
given SP level require that the SP itself be installed is incorrect.

Bruce