VBA Problems ... (since windows update?)

[QB]

I am running winXP with Office 2003 and 2007 and am currently working on a
2003 db (using this one as an example, but problem is on a multitude of dbs
as of late).

The db was working fine for at least a month (if not longer) and now I get
errors? For instance, I use the following to work with Word.

*************
Dim objWord As Object

On Error Resume Next
Set objWord = GetObject(, "Word.Application")
DoEvents
If Err.Number <> 0 Then
On Error GoTo 0
Err.Clear
DoEvents
Set objWord = CreateObject("Word.Application")
Else
objWord.Quit
DoEvents
Set objWord = CreateObject("Word.Application")
End If

On Error GoTo Error_Handler
....
*************

What once worked, not generates and error highlighting Set objWord =
GetObject(, "Word.Application") and stating that the ActiveX control cannot
create object (err 429). Why is it not performing the Resume Next????? It
is failing on simple Trim() commands....

I could believe 1 db could be corrupted, but this is now a wide spread issue
on at least 6 different dbs.

Can this be linked to recent windows updates (it is the only thing that has
changed in recent days/weeks)? If so, how do you determine the source?

Thank you for the help,

QB

 

[vanderghast]

Check the references. One that is checked is probably labeled MISSING in its
description (hard to miss once you display the Tools | References ... ).
Even if it has NOTHING to do with Trim( ) or what you are doing, that
missing reference is checked for its presence and THAT fails! Resolve it (or
uncheck it).

Vanderghast, Access MVP

 

[QB]

This is not a reference issue. Already checked.

Thank you for trying. Any other ideas?

QB

 

[QB]

I should mention that:
a) I checked nothing is marked as missing in the references dialog
b) I checked the reference files (dll,ocx,...) are where they say they are
QB

 

[QB]

One last set of info.

1. The db compiles without any issue.
2. Done a compact and repair
3. I have remove all references (except for the 2 default one: vba &
access), and I get the same error regarless.

QB

 

[QB]

Did some more troubleshooting.

I performed a repair on the office installations. No change.
I performed an office diagnostic, found a problem and resolved it. No change.
I tested on another machine and the dbs all work fine.

I do tend to believe it is a reference issue, but access is not flagging any
problems?! Can they become corrupt? Is there a way to check?

Anyone ever seen anything like this before?

QB

 

[vanderghast]

There are more than 2 references, by default, if memory serves, on a fresh
installation.

Furthermore, if you have and Access 2003 and Access 2007 on the same
machine, you MAY have a conflict of installation in the registry (but not
necessary).


I would suggest to uninstall and re-install the Access versions, with all
the relevant Service Packs, at least, on the computer showing that problem.
Sure, that may not be the easiest solution, it is time consuming, and
nothing say it would run nice after that either... but if no one else has an
idea...

Note that I am quite surprised that you have ONLY two references. From
memory, it is 4, if not 5 (if ADO is included too).


Vanderghast, Access MVP

 

[QB]

I completly uninstalled both 2003 and 2007 and reinstalled. No effect, same
issue.

I'm about ready to pull my hair out.
I've even gone to the point of uninstalling all the recent Win Updates...

I am 99% sure the source of the problem came from an update, as this is the
only change to occur on this machine, but can't seem to fix it.

My next choice, unless someone tells me otherwise, will be a format!
Unbelieveable!!! This is starting to make me re-evaluate continuing to work
with access altogether.

QB

 

[Dirk Goldgar]

I completly uninstalled both 2003 and 2007 and reinstalled. No effect,
same
issue.

I'm about ready to pull my hair out.
I've even gone to the point of uninstalling all the recent Win Updates...

I am 99% sure the source of the problem came from an update, as this is
the
only change to occur on this machine, but can't seem to fix it.

My next choice, unless someone tells me otherwise, will be a format!
Unbelieveable!!! This is starting to make me re-evaluate continuing to
work
with access altogether.

In the VBA Editor environment, open the Tools -> Options... dialog, go to
the General tab, and inspect the value of the "Error Trapping" option. Is
it set to "Break on All Errors"? If so, set it to "Break on Unhandled
Errors".

 

[Jeanette Cunningham]

I believe many people have both A2003 and A2007 installed on the same WinXP
computer without any problems, as I do.
Sounds like something peculiar to your computer - you have my sympathy, as
it is such a time consuming problem to deal with.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[QB]

Don't take this the wrong way, but I could kiss you right now!!!!

So how did the value get changed? I didn't know about the form/menu.
Anyways, at least the problem is resolved. Hey, I only lost half a days work
at a time when I have a dealine to meet... no biggy...

Dirk, any chance you want to give me your phone number for future
emergencies! LOL.

Thank you, Thank you, Thank you!

QB

 

[Dirk Goldgar]

Don't take this the wrong way, but I could kiss you right now!!!!

LOL
It's a kind offer, but my wife might object.

So how did the value get changed? I didn't know about the form/menu.

I don't know. If you're sure you didn't change it, for *any* VBA-using
application, I don't know how it could have gotten changed. Bear in mind
that this same setting governs not only Access, but Word, Excel, and any
other VBA-using applications. If you change it in one, you change it for
them all.

Dirk, any chance you want to give me your phone number for future
emergencies! LOL.

Only if you want to pay my consulting rates.

Thank you, Thank you, Thank you!

You're very welcome.

 

[David W. Fenton]

I believe many people have both A2003 and A2007 installed on the
same WinXP computer without any problems, as I do.
Sounds like something peculiar to your computer

Running A2007 while A2003 is already running can cause the
pre-existing instance of A2003 to fail to work properly. I've had it
happen. The solution is to exist A2003 and restart it so that it
re-registers itself. I've never had the opposite problem, i.e.,
A2007 crapping out because A2003 had registered itself after A2007
was started.

 

[Jeanette Cunningham]

On my computer, it is not possible to open A2007 while a database is already
open in A2003 and vice versa.
Is this what you meant David?


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[David W. Fenton]

On my computer, it is not possible to open A2007 while a database
is already open in A2003 and vice versa.
Is this what you meant David?

You can't do it by doubleclicking a file, but if you start A2007
itself you can then open databases in it while A2003 is open (and
vice versa), so no, that's not what I meant.