2003 Repair / Compact Problem

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

With 2007 & 2003 Co-Exiting on the same machine, I can no longer
repair & compact my 2003 .adp files. I realize there are known issues with
having both on the same machine but did not know about this one. Is this a
known problem or does anyone have a fix for it?

Thanks in advance,
bob mcclellan
 
Hi Bob,

Just to confirm, I am running A2002/A2003 and A2007 on Vista and have
experienced the same problem, although, it is itermittent, but more frequent
than not. Haven't tried XP, which I use as my SQL Server 2000 Server
platform, as according to MS, Vista doesn't fully support SQL Server 2000,
but will do, the symptoms are that an application gets an Unresponsive
error.

I am also experiencing more A2007 database corruptions than I would expect
which I ususually solve by Importing all the objects into a clean ADP,
although frequently that also gets an Unresponsive error as well.

Will investigate further if I have them time.

Comments/Thoughts anyone?

Cheers
Guy
 
I too am having the problem, my large ADP will blow up ever time, the
smaller MDB's may or may not crash when compacting or closing the database
window. I just removed Access 2007 from my Vista 64bit machine but the
problem stayed. Not sure if it is because 2007 didn't remove everything, or
if it wasn't even causing the problem. Sure hope if either you or Guy find
the problem you post the answer. My error message is Microsoft Office Access
has stopped working.

The good news is the problem has me saving my work more often..

Bill

Hi Bob,

Just to confirm, I am running A2002/A2003 and A2007 on Vista and have
experienced the same problem, although, it is itermittent, but more frequent
than not. Haven't tried XP, which I use as my SQL Server 2000 Server
platform, as according to MS, Vista doesn't fully support SQL Server 2000,
but will do, the symptoms are that an application gets an Unresponsive
error.

I am also experiencing more A2007 database corruptions than I would expect
which I ususually solve by Importing all the objects into a clean ADP,
although frequently that also gets an Unresponsive error as well.

Will investigate further if I have them time.

Comments/Thoughts anyone?

Cheers
Guy
 
Bill, Bob,

Forgot to mention that I also frequently get an application Unresponsive
Error making an ADE.

The only additional information I can offer at this point, as I haven't
investigated the problem to any extent, is that I also get an application
unresponsive error looping through the Reports Collection to programatically
set, as opposed to manually setting, the Ribbon Name. It fails somewhere
between the 3rd and 10th iteration through the loop. However, and this is
very strange, from memory I did get it to work on XP, although, this maybe
just the intermittent nature of the issue and I was lucky.

Assuming, perhaps incorrectly, that there maybe some common functionality
between compacting/importing and making an ADE there maybe a common thread
here.

Allen Browne MVP suggested checking that your run permissions are
Administrator, but haven't tried this yet.

Guy
 
Thanks for the quick reply. I have only used 2007 for some testing of
existing apps to figure if I am going to have problems as my clients update.
The ribbon got in the way but can be removed when the app opens, other than
that it seems to work. The crashes (my term for when an app quits) occur on
both access xp and 2003, the only difference is when xp crashes I get a
little note from MS suggesting I upgrade to 2003. I don't get any kind
suggestions when 2003 dumps. Oh yes I do run with admin rights. No help. I'm
really not sure the problem is with 2007, could be Vista, 64 bit or some
other software I have installed.

Bill
Bill, Bob,

Forgot to mention that I also frequently get an application Unresponsive
Error making an ADE.

The only additional information I can offer at this point, as I haven't
investigated the problem to any extent, is that I also get an application
unresponsive error looping through the Reports Collection to programatically
set, as opposed to manually setting, the Ribbon Name. It fails somewhere
between the 3rd and 10th iteration through the loop. However, and this is
very strange, from memory I did get it to work on XP, although, this maybe
just the intermittent nature of the issue and I was lucky.

Assuming, perhaps incorrectly, that there maybe some common functionality
between compacting/importing and making an ADE there maybe a common thread
here.

Allen Browne MVP suggested checking that your run permissions are
Administrator, but haven't tried this yet.

Guy
 
Another thought just occurred to me, since we seem to be the only 3 people
in the world with the problem perhaps there is another explanation. Most of
the error's occur when making ade/mde compact and repair all of which create
temporary files. Could it be hard drive drivers? Any for comparison I am
running the following hardware
Dell XPS 410
2 250G SATA hard drives configured raid 0
Intel Raid controller
Intel Matrix storage console?
nVidia 8600 video card, but I had the problem with the nVidia 7300LE
E6600 duo core processor
and 4 G of ram.

Hope this creates a clue

Bill

Hi Bob,

Just to confirm, I am running A2002/A2003 and A2007 on Vista and have
experienced the same problem, although, it is itermittent, but more frequent
than not. Haven't tried XP, which I use as my SQL Server 2000 Server
platform, as according to MS, Vista doesn't fully support SQL Server 2000,
but will do, the symptoms are that an application gets an Unresponsive
error.

I am also experiencing more A2007 database corruptions than I would expect
which I ususually solve by Importing all the objects into a clean ADP,
although frequently that also gets an Unresponsive error as well.

Will investigate further if I have them time.

Comments/Thoughts anyone?

Cheers
Guy
 
Bill wish I had a development environment like yours :-)

Can't really comment of potential driver issues other than I would expect
the O/S and other applications to experience problems as well.

Will try and find some time to investigate further.

Guy
 
Well that was certainly easier than changing out my hard drives.

Bill
Bill wish I had a development environment like yours :-)

Can't really comment of potential driver issues other than I would expect
the O/S and other applications to experience problems as well.

Will try and find some time to investigate further.

Guy
 
Bill, Bob,

Investigated further and believe the problem is that you need to "Run as
Administrator".

Right mouse click your shortcut "Run as Administrator" or to set it
permanently right mouse click/shortcut tab/advanced and check the Run as
Administrator checkbox.

Currently I'm logged onto a Domain on which I don't have Administrator
rights, but I do have local Administrator rights and UAC turned off, so not
exactly sure why this should still require that I "Run as Administrator" for
particular Access actions. However, still coming up to speed on Windows
Vista, and don't currently have the time to research the reasons behind it,
but I am sure there is a perfectly logical reason. Maybe someone will
enlighten us.

Thanks Alan Browne (MVP) for that thought, I wonder if looping through the
reports collection now also works?

Cheers
Guy
 
Bill, Bob,

I believe I have resolved the problem and that is that you do indeed need to
"Run as Administrator".

Right mouse click your MS Access shortcut (or the executable) - "Run as
Administrator", or to always "Run as Administrator" right mouse
click/shortcut tab/advanced and check "Run as Administrator".

Currently I have Windows Vista UAC turned off, therefore not sure, without
doing further research, as to why performing actions such as compact repair
and make ade within Access cause an "Unresponsive error", although, I am
confident that there is perfectly logical explanation. I would assume that
if you have UAC turned on then you will be prompted for confirmation of
those actions, and others considered a security threat, by the UAC (I
haven't tried it).

Still getting up to speed on Vista, but I'm sure there will plenty more
Vista learning expriences for developers to consider, not least of which
will be the UAC.

I wonder if looping through the reports collection now works? Must try it.

Let me know if this solves your problem.
Guy
 
Guy,

Well I guess thinking we had the same problem was in error. My shortcuts are
already set to run as administrator.

Thanks for the feedback and assistance, for a while I didn't feel all alone,
course that may not fix Bob's problem ether.
..


Bill

Bill, Bob,

I believe I have resolved the problem and that is that you do indeed need to
"Run as Administrator".

Right mouse click your MS Access shortcut (or the executable) - "Run as
Administrator", or to always "Run as Administrator" right mouse
click/shortcut tab/advanced and check "Run as Administrator".

Currently I have Windows Vista UAC turned off, therefore not sure, without
doing further research, as to why performing actions such as compact repair
and make ade within Access cause an "Unresponsive error", although, I am
confident that there is perfectly logical explanation. I would assume that
if you have UAC turned on then you will be prompted for confirmation of
those actions, and others considered a security threat, by the UAC (I
haven't tried it).

Still getting up to speed on Vista, but I'm sure there will plenty more
Vista learning expriences for developers to consider, not least of which
will be the UAC.

I wonder if looping through the reports collection now works? Must try it.

Let me know if this solves your problem.
Guy
 
Guy, Bill,
Running as administrator did not fix my problem (also intermittent and it
happens more than not )
My UAC was already turned off.
I will post any additional findings on this.
My problem is not an unresponsive one. I get

Microsoft Office Access Has Stopped Working
-Check online for a solution and close the program
-Close the program
-Debug the program

Thanks for the shared findings,
Bob.
 
Additionally meant to send this

Microsoft Office Access Has Stopped Working
-Check online for a solution and close the program
-Close the program
-Debug the program

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 11.0.6566.0
Application Timestamp: 42cdb33e
Fault Module Name: StackHash_babb
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: babb
Additional Information 2: bc9a90e7ae14ed823839ded297bea405
Additional Information 3: 8a19
Additional Information 4: e63618dd7c395abb06f520978a97fe85
 
Bob, Bill,

Thanks for the additional feedback.

I wonder why it "appears" to have resolved my problem and not yours.

I managed to compact/repair and build an ADE without incident several times
after "Running as Administrator". I accept this is hardly extensive testing,
but it wasn't something I had been able to do with any consistancy before.
Although, I am curious as to why with the UAC turned off "Running as
Administrator" should have any impact.

The only other input I can provide, at this stage, is that I am running a
similar environment on Windows XP (ie. A2002/A2003 and A2007 + SQL Server
2000) and it all works as expected.

Oh well another idea shot down in flames. I'm sure it wont be the last :-)

Likewise will post any additional thoughts I have to this newsgroup.

Cheers
Guy
 
Gents,

Thanks for the additional feedback.

I wonder why it "appears" to have resolved my problem and not yours?

When "Running as Administrator" I as was able to compact/repair and make an
ADE several times without incident, which I accept is not extensive testing,
but it was something that I couldn't perform with any consistancy
previously. I am also curious as to why "Running a Administrator" should
have any impact with the UAC turned off.

The only other input I have is that I am running a similar environment on
Windows XP (ie. A2002/A2003/A2007 and SQL Server 2000) and it all works as
expected.

If time permits I will check the MS Access blog to see if there is any
information on this issue.

Slyvain, David any thoughts?

Oh well another idea shot down in flames, I'm sure it won't be the last :-)

Cheers
Guy
 
Gents,

Forgot to mention there are still plenty of options to try such as:

1) Uninstalling the prior versions of Access
2) Turning on UAC

and so on. Of course these may not be viable options for your
development/production environments, but in the interim they may help to
narrow the scope of the issue.

Haven't got time today to investigate further.

Cheers
Guy
 
Bob,

I Don't know If you have solved this problem, but this fixed it for me. I
uninstalled Office 2003 (I only had Access installed), and reinstalled it
and tested it. Compact and repair worked and the other issue that failed
every time was right clicking on the menu and selecting customize. By the
way it would fail sometimes in MDB's but all the time in an ADP.

Anyway I digress after installing I checked and the problem was gone. Then
when Windows update offered to install sp2 I let it. Guess what, the problem
returned. I uninstalled it again, and this time just installed SP 1 and it
seems to be working fine. I'm not sure what SP 2 was supposed to do for
Access but for the time being I'll run with out it.

Oh one other thing that may have had an effect is I removed Access XP too. I
doubt this had any effect but thought I should mention it.


Bill

PS I'll try and send this to your personal email as well


Additionally meant to send this

Microsoft Office Access Has Stopped Working
-Check online for a solution and close the program
-Close the program
-Debug the program

Problem signature:
Problem Event Name: APPCRASH
Application Name: MSACCESS.EXE
Application Version: 11.0.6566.0
Application Timestamp: 42cdb33e
Fault Module Name: StackHash_babb
Fault Module Version: 6.0.6000.16386
Fault Module Timestamp: 4549bdc9
Exception Code: c0000374
Exception Offset: 000af1c9
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: babb
Additional Information 2: bc9a90e7ae14ed823839ded297bea405
Additional Information 3: 8a19
Additional Information 4: e63618dd7c395abb06f520978a97fe85
 
Bill Patten said:
Well that was certainly easier than changing out my hard drives.

Bill
Bill wish I had a development environment like yours :-)

Can't really comment of potential driver issues other than I would expect
the O/S and other applications to experience problems as well.

Will try and find some time to investigate further.

Guy
Click to expand...
 
Back
Top