Problem with mouse over graphics

[Jan Il]

Hi all - Access 2002 XP, Windows ME

I have a database that I created in 2000, and have now switched over to
2002XP. When I open this database, there is an Opening form with two
graphics used as command buttons. I have a mouse over with a Raise graphic
and a Flatten all graphics macros in the form properties. They work fine in
2000, but, when I open the database in 2002, I get an error box that say
Error with DLL. When I click OK, the detail box comes up and references the
Raise graphic and then Flatten all graphics codes. In order to be able to
get the db to function, I had to delete these macros, thus, now I have no
mouse overs. I tried to recreate the mouse over but it won't work at all in
2002. Is this a feature that is not supported in 2002?

I would truly appreciate any suggestions or information on this issue.

Best regards,
Jan

 

[Dirk Goldgar]

Hi all - Access 2002 XP, Windows ME

I have a database that I created in 2000, and have now switched over
to 2002XP. When I open this database, there is an Opening form with
two graphics used as command buttons. I have a mouse over with a
Raise graphic and a Flatten all graphics macros in the form
properties. They work fine in 2000, but, when I open the database in
2002, I get an error box that say Error with DLL. When I click OK,
the detail box comes up and references the Raise graphic and then
Flatten all graphics codes. In order to be able to get the db to
function, I had to delete these macros, thus, now I have no mouse
overs. I tried to recreate the mouse over but it won't work at all
in 2002. Is this a feature that is not supported in 2002?

I would truly appreciate any suggestions or information on this issue.

Best regards,
Jan

Jan -

Is this the MOW database of which I have a copy? The special effects
work fine for me in Access 2002.

 

[Jan Il]

Hi Dirk!

Jan -

Is this the MOW database of which I have a copy? The special effects
work fine for me in Access 2002.

Yes, that's one of them. This is one that was originally created in 2000 and
is run in both 2000 and 2002. When I first open the db 2002, if I have the
cursor anywhere on the face of the form, I get the "Error in loading DLL"
message, and then it's like trying to get gum from a hot sidewalk off the
bottom of your shoe to get all the following errors to stop. I finally had
to disable the effects in order to get past the opening page. I had to
reinstall 2002 to solve a PowerPoint problem. I opened a copy of the MOW db
yesterday for the first time since then, and the effects went bonkers. If I
knew what DLL it's pitching the fit about, I might know where to try to
correct the problem.

I can't get anywhere with the effects activated, and the error message is
really very vague...it just says "Error in loading DLL", then when I click
OK, it shows me the details box that displays 'Raise Wayside graphic', when
I hit Escape a bazillion times to finally get it to close that box, the
whole wazoolie with the gum on the shoe starts again. If I'm really lucky,
and manage to get the cursor off the form before another round starts, then
I can go to the design view and delete the macros in the form properties and
stop the errors. The Help just references mostly D&R and install stuff that
I've tried but, no help. It doesn't tell me what the error message really
means, or what to look for regarding the DLL. It does not do this when I
open it in 2000 at work.

Thank you for your time and help. I really appreciate it.

Jan

 

[Dirk Goldgar]

Hi Dirk!



Yes, that's one of them. This is one that was originally created in
2000 and is run in both 2000 and 2002. When I first open the db
2002, if I have the cursor anywhere on the face of the form, I get
the "Error in loading DLL" message, and then it's like trying to get
gum from a hot sidewalk off the bottom of your shoe to get all the
following errors to stop. I finally had to disable the effects in
order to get past the opening page. I had to reinstall 2002 to solve
a PowerPoint problem. I opened a copy of the MOW db yesterday for the
first time since then, and the effects went bonkers. If I knew what
DLL it's pitching the fit about, I might know where to try to correct
the problem.

I can't get anywhere with the effects activated, and the error
message is really very vague...it just says "Error in loading DLL",
then when I click OK, it shows me the details box that displays
'Raise Wayside graphic', when I hit Escape a bazillion times to
finally get it to close that box, the whole wazoolie with the gum on
the shoe starts again. If I'm really lucky, and manage to get the
cursor off the form before another round starts, then I can go to the
design view and delete the macros in the form properties and stop the
errors. The Help just references mostly D&R and install stuff that
I've tried but, no help. It doesn't tell me what the error message
really means, or what to look for regarding the DLL. It does not do
this when I open it in 2000 at work.

So the problem first appeared after you reinstalled Office 2002? I
suspect something changed in that installation, probably the location of
some supporting DLL. I have a vague feeling I've seen this message
reported before in similar circumstances. I'll do little research and
get back to you. In the mean time, try checking and verifying your
references using Doug Steele's instructions from


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Since this is happening on your startup form, you'll need to hold down
the Shift key as you open the database so as to suppress the processing
of the Startup properties. If the References dialog doesn't show any
broken references, go all the way through the process of checking and
unchecking some random reference, as instructed on the web page I
referred to.

Let me know if that fixes the problem, while I check for other possible
solutions.

 

[Jan Il]

Hi Dirk,

So the problem first appeared after you reinstalled Office 2002? I
suspect something changed in that installation, probably the location of
some supporting DLL. I have a vague feeling I've seen this message
reported before in similar circumstances. I'll do little research and
get back to you. In the mean time, try checking and verifying your
references using Doug Steele's instructions from

Yes...just since the reinstall of '02. It has been working fine before.
I'll check the references here,

Since this is happening on your startup form, you'll need to hold down
the Shift key as you open the database so as to suppress the processing
of the Startup properties. If the References dialog doesn't show any
broken references, go all the way through the process of checking and
unchecking some random reference, as instructed on the web page I
referred to.

Let me know if that fixes the problem, while I check for other possible
solutions.

'k...I'll open as you instructed, and check all the References too. In the
words of our new Governor "I'll be back..." ;-)

Jan

 

[Jan Il]

Hi Dirk -

So the problem first appeared after you reinstalled Office 2002? I
suspect something changed in that installation, probably the location of
some supporting DLL. I have a vague feeling I've seen this message
reported before in similar circumstances. I'll do little research and
get back to you. In the mean time, try checking and verifying your
references using Doug Steele's instructions from


http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html

Since this is happening on your startup form, you'll need to hold down
the Shift key as you open the database so as to suppress the processing
of the Startup properties. If the References dialog doesn't show any
broken references, go all the way through the process of checking and
unchecking some random reference, as instructed on the web page I
referred to.

Let me know if that fixes the problem, while I check for other possible
solutions.

'k...I checked all the References according to Doug Steele's site, and there
are none with Missing in front of them, and all the necessary References are
checked. In the related site for the 2002 Article 286300 reference, the
BrokenReference Property part, when I went typed in
?Application.BrokenReference in the Immediate window and hit enter I got the
an error message that said;

"Compile error.
Error in loading DLL"

I did some more troubleshooting in reference to the error message, but, it
still just gives me vague information regarding references. Since it is in
response to the Macros for Raise Wayside Graphic of the graphic command
button, and Flatten all graphics in the Form Properties On Mouse Move event,
I'm a bit confused with this error??

Jan

 

[Dirk Goldgar]

Hi Dirk,

Yes...just since the reinstall of '02. It has been working fine
before. I'll check the references here,

'k...I'll open as you instructed, and check all the References too.
In the words of our new Governor "I'll be back..." ;-)

If that doesn't correct the problem, the next thing I'd try is
reregistering DAO. To do that, follow these steps:

1. Closing all open instances of Access.

2. On the the Windows task bar, click Start -> Run...

3. Enter the following in the Run dialog box:

regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll"

Note -- the above may have been wrapped by the newsreader, but it was
entered all on one line. Also note that the path *may* be different on
your PC, though the above is standard. However, if regsvr32 says it
can't find the file, you may have to search your hard drive for the file
and put the correct path into Run box.

If neither this nor my previous suggestion about references works, we'll
try something more drastic.

 

[Dirk Goldgar]

Hi Dirk -



'k...I checked all the References according to Doug Steele's site,
and there are none with Missing in front of them, and all the
necessary References are checked. In the related site for the 2002
Article 286300 reference, the BrokenReference Property part, when I
went typed in ?Application.BrokenReference in the Immediate window
and hit enter I got the an error message that said;

"Compile error.
Error in loading DLL"

I did some more troubleshooting in reference to the error message,
but, it still just gives me vague information regarding references.
Since it is in response to the Macros for Raise Wayside Graphic of
the graphic command button, and Flatten all graphics in the Form
Properties On Mouse Move event, I'm a bit confused with this error??

That suggests to me that the reference to the Microsoft Access 10.0
Object Library itself may be broken, but it may just be that some other
broken reference is preventing that one from being resolved. Still, it
wouldn't hurt to search your hard disk for the location of the file
"msacc.olb", and see if it is found where it the References dialog
expects it.

When you were in there checking the references, did you take the
recommended step of checking some reference at random, then closing the
dialog, then opening the dialog again and unchecking that reference?

 

[Jan Il]

If that doesn't correct the problem, the next thing I'd try is
reregistering DAO. To do that, follow these steps:

1. Closing all open instances of Access.

2. On the the Windows task bar, click Start -> Run...

3. Enter the following in the Run dialog box:

regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll"

Note -- the above may have been wrapped by the newsreader, but it was
entered all on one line. Also note that the path *may* be different on
your PC, though the above is standard. However, if regsvr32 says it
can't find the file, you may have to search your hard drive for the file
and put the correct path into Run box.

On my way...

If neither this nor my previous suggestion about references works, we'll
try something more drastic.

Ahmm...'k...8-o..

 

[Jan Il]

Hi Dirk,

If that doesn't correct the problem, the next thing I'd try is
reregistering DAO. To do that, follow these steps:

1. Closing all open instances of Access.

2. On the the Windows task bar, click Start -> Run...

3. Enter the following in the Run dialog box:

regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll"

'k..here is the results of this one......I now have an error message when
opening the db in the Opening Form that says;

"The object doesn't contain the Automation object *|.*

You tried to run a Visual Basic procedure to set a property or method for an
object.
However, the component doesnt't make the property method available for
Automation operations.

Check the component's documentation for information on the properties and
methods it makes available for Automation operations."

I got no error message after entering the information in the Run dialog box,
so all appeared to work as you expected.

Jan

 

[Jan Il]

That suggests to me that the reference to the Microsoft Access 10.0
Object Library itself may be broken, but it may just be that some other
broken reference is preventing that one from being resolved. Still, it
wouldn't hurt to search your hard disk for the location of the file
"msacc.olb", and see if it is found where it the References dialog
expects it.

When I checked again, since doing the changes as instructed in your previous
message, the Microsoft Access 10.0 Object Library is no longer available,
only the Microsoft Access 9.0 Object Library, which is now checked. The 10.0
is no longer showing up in the list...but, it was earlier...and in the place
where the 9.0 now is in the list..???

The mascc.olb is in the C:\Program Files\Microsoft Office\Office
10...ahmm...but, I'm not sure how I check to see if this is where the
References expects it to be..as I have not seen anything that indicated a
location of a file. But, is this as it *should* be?

Jan

 

[Dirk Goldgar]

When I checked again, since doing the changes as instructed in your
previous message, the Microsoft Access 10.0 Object Library is no
longer available, only the Microsoft Access 9.0 Object Library, which
is now checked. The 10.0 is no longer showing up in the list...but,
it was earlier...and in the place where the 9.0 now is in the
list..???

The mascc.olb is in the C:\Program Files\Microsoft Office\Office
10...ahmm...but, I'm not sure how I check to see if this is where the
References expects it to be..as I have not seen anything that
indicated a location of a file. But, is this as it *should* be?

No, it most certainly is *not*. Access 9.0 = Access 2000, and you told
me you were running Access 2002. Do you have both Access 2000 and
Access 2002 installed on your system? This is perfectly feasible -- I
do, for example -- but the two installations have to be kept carefully
separate. I suspect we have a problem with mixed versions among the
DLLs Access relies on.

 

[Jan Il]

No, it most certainly is *not*. Access 9.0 = Access 2000, and you told
me you were running Access 2002. Do you have both Access 2000 and
Access 2002 installed on your system? This is perfectly feasible -- I
do, for example -- but the two installations have to be kept carefully
separate. I suspect we have a problem with mixed versions among the
DLLs Access relies on.

No, I am not using 2000 and 2002 separately at this time. I was told when I
first got my 2002 Upgrade that I should not do an Upgrade, but to install
2002 to a separate folder and NOT to let it delete the 2000 version. I did
a custom install, making sure that the 2002 was installed to a separate
folder, Office 10, opposed to the Office folder where 2000 was. But, it
seemed that 2002 kept trying to usurp 2000 at every curve, and it became
such a problem that I decided to uninstall 2002, then reintall it and just
do the Upgrade and allow the Lionfish to prevail over the Guppy. But, now
when I open Access I am getting this problem with the special effects. All
other things do seem to work ok so far, but, I can't understand why the
special effects are acting up like this. I can only wonder what other
functions that I have not tried yet may later come into play.

Right now, since I did the D&R a bit ago, the 10.0 is back, and I am no
longer getting that other error message...just back to the Error in loading
DLL. I just seems strange that after I put the path information you gave me
into the Run dialog box, then rebooted, when I opened the db I got that new
error message (which I did a screen shot of for reference). But, after I
did the D&R, all things were back to square one again, with just the Error
in loading DLL, and then when I checked the References again, the 10.0 was
back again. And noooo...I have not been sniffing glue, or inhaling any
funny air drafts ... ;-)))

Jan

 

[Jan Il]

Hi Dirk,

That suggests to me that the reference to the Microsoft Access 10.0
Object Library itself may be broken, but it may just be that some other
broken reference is preventing that one from being resolved. Still, it
wouldn't hurt to search your hard disk for the location of the file
"msacc.olb", and see if it is found where it the References dialog
expects it.

When you were in there checking the references, did you take the
recommended step of checking some reference at random, then closing the
dialog, then opening the dialog again and unchecking that reference?

I have had a chance to do some other troubleshooting, and have found a
couple of interesting items;

1) While taking the References I have in use one by one and unchecking them,
closing the dialog, then opening and rechecking and such according to Doug's
instructions, I found that the Microsoft Access Wizard Control Library, once
unchecked, no longer appears in the Reference list. The rest, at least
those I could uncheck, and then went back, were still in the list and I
could recheck them. Interesting, but, don't know if it really means that
much in regards to the problem.

2) While checking some of the other forms in the db, I found that all the
command buttons, when clicked, gave an error message;

The expression On Activate you entered as the event property setting
produced the following error: Error in loading DLL
*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
*There may have been an error evaluating the function, event or macro.

This error message shows up on most of forms when I click a command button.
Some, such as the Main Switchboard Form and Defect Filter Form, will go
ahead and open the associated form when you click ok on the error box, but
others, such as the Wayside Inspections Menu form won't open the related
form.

In checking the referenced On Activate in the form Properties, most simply
have the following Event Procedure;
Me!Text62 = Null
Me!Text64 = Null

(Text 62 and Text 64 being the two date text boxes on the form)

I don't understand why they work just fine in 2000, but now are creating
this
kind of problem in 2002 XP. But, every time I open Access, Word or
PowerPoint
XP, I get a dialog box that says it is installing Microsoft components
and features. I have checked and everything has been set to 'Run from my
computer'. Yet, I don't get this message when I open Excel XP.

Well....I don't know if all this is of any help, but, that is what I have
found so far.

Jan

 

[Dirk Goldgar]

No, I am not using 2000 and 2002 separately at this time. I was told
when I first got my 2002 Upgrade that I should not do an Upgrade, but
to install 2002 to a separate folder and NOT to let it delete the
2000 version. I did a custom install, making sure that the 2002 was
installed to a separate folder, Office 10, opposed to the Office
folder where 2000 was. But, it seemed that 2002 kept trying to usurp
2000 at every curve, and it became such a problem that I decided to
uninstall 2002, then reintall it and just do the Upgrade and allow
the Lionfish to prevail over the Guppy. But, now when I open Access I
am getting this problem with the special effects. All other things do
seem to work ok so far, but, I can't understand why the special
effects are acting up like this. I can only wonder what other
functions that I have not tried yet may later come into play.

Right now, since I did the D&R a bit ago, the 10.0 is back, and I am
no longer getting that other error message...just back to the Error
in loading DLL. I just seems strange that after I put the path
information you gave me into the Run dialog box, then rebooted, when
I opened the db I got that new error message (which I did a screen
shot of for reference). But, after I did the D&R, all things were
back to square one again, with just the Error in loading DLL, and
then when I checked the References again, the 10.0 was back again.
And noooo...I have not been sniffing glue, or inhaling any funny air
drafts ... ;-)))

<g>
I can see how the different Office installs could have gotten entangled,
since MS Office extends its tentacles practically everywhere. It's
probably possible -- theoretically, at least -- to attack the specific
problem by tracking down all the DLLs and registry entries, finding the
error(s), and fixing them. But I *think* the best and safest approach
at this point is to

1. Uninstall and *completely* remove Office XP.

2. Uninstall (if necessary) and *completely* remove Office 2000.

3. Reinstall Office XP.

Note that "completely removing" Office involves more than just
uninstalling it. There are KB articles with instructions and a utility
for doing this with Office 2000, but I don't see one for Office XP, and
I don't know what that means. I'm going to do a bit more research
before pointing them to you and recommending that you proceed.

 

[Dirk Goldgar]

I have had a chance to do some other troubleshooting, and have found a
couple of interesting items;

1) While taking the References I have in use one by one and
unchecking them, closing the dialog, then opening and rechecking and
such according to Doug's instructions, I found that the Microsoft
Access Wizard Control Library, once unchecked, no longer appears in
the Reference list. The rest, at least those I could uncheck, and
then went back, were still in the list and I could recheck them.
Interesting, but, don't know if it really means that much in regards
to the problem.

2) While checking some of the other forms in the db, I found that all
the command buttons, when clicked, gave an error message;

The expression On Activate you entered as the event property setting
produced the following error: Error in loading DLL
*The expression may not result in the name of a macro, the name of a
user-defined function, or [Event Procedure].
*There may have been an error evaluating the function, event or macro.

This error message shows up on most of forms when I click a command
button. Some, such as the Main Switchboard Form and Defect Filter
Form, will go ahead and open the associated form when you click ok on
the error box, but others, such as the Wayside Inspections Menu form
won't open the related form.

In checking the referenced On Activate in the form Properties, most
simply have the following Event Procedure;
Me!Text62 = Null
Me!Text64 = Null

(Text 62 and Text 64 being the two date text boxes on the form)

I don't understand why they work just fine in 2000, but now are
creating this
kind of problem in 2002 XP. But, every time I open Access, Word or
PowerPoint
XP, I get a dialog box that says it is installing Microsoft components
and features. I have checked and everything has been set to 'Run from
my computer'. Yet, I don't get this message when I open Excel XP.

Well....I don't know if all this is of any help, but, that is what I
have found so far.

Plainly your installation of Office XP is messed up. I wouldn't worry
too much about the individual symptoms at this point. As I said in my
most recent message in the other subthread, I'm looking into the best
procedure to completely all traces of both versions of Office so that
you can reinstall.

 

[Jan Il]

Hi Dirk,

"> >

<g>
I can see how the different Office installs could have gotten entangled,
since MS Office extends its tentacles practically everywhere. It's
probably possible -- theoretically, at least -- to attack the specific
problem by tracking down all the DLLs and registry entries, finding the
error(s), and fixing them. But I *think* the best and safest approach
at this point is to

1. Uninstall and *completely* remove Office XP.

2. Uninstall (if necessary) and *completely* remove Office 2000.

3. Reinstall Office XP.

Note that "completely removing" Office involves more than just
uninstalling it. There are KB articles with instructions and a utility
for doing this with Office 2000, but I don't see one for Office XP, and
I don't know what that means. I'm going to do a bit more research
before pointing them to you and recommending that you proceed.

'k.....I'll just stand pat until you give further instructions on how best
to proceed. Your following message below understood as well.

Jan

 

[Dirk Goldgar]

Hi Dirk,

"> >

'k.....I'll just stand pat until you give further instructions on how
best to proceed. Your following message below understood as well.

Jan -

It looks like Office XP does a better job of cleaning up after itself
than Office 2000 does, so you don't need to do quite as much. Still, I
think these are the steps you should follow -- provided that you don't
also have Office/Access 97 installed on this PC, and you want to remove
all vestiges of both Office XP and 2000 before reinstalling:

1. Use Add/Remove Programs from the Control Panel to uninstall Office
XP.

2. Try to use the Add/Remove Programs applet to uninstall Office 2000.
Because of your install history, I'm not sure whether this is going to
be available to you or not.

3. Use the Windows Installer Cleanup Utility, available from this page:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;290301

to clean up any registry settings related to the installation of OXP.
Note that there are two versions of this utility, one for Win98/ME and
one for WinNT/2K. Choose the right one and follow the instructions.

4. Reboot.

5. Look on the Office XP CD for a file called offclean.exe. Run that
utility.

6. (This step may be overkill) Look on the Office *2000* CD for a file
called offclean.exe, and run *that* if you find it.

7. Download and run the Eraser2k utility from

http://support.microsoft.com/default.aspx?scid=kb;EN-US;239938

8. Assuming all this went well, reboot; then reinstall Office XP.
Choose the default
folder for installation, unless you have a good reason to do otherwise.

 

[Jan Il]

I can see how the different Office installs could have gotten

Jan -

It looks like Office XP does a better job of cleaning up after itself
than Office 2000 does, so you don't need to do quite as much. Still, I
think these are the steps you should follow -- provided that you don't
also have Office/Access 97 installed on this PC, and you want to remove
all vestiges of both Office XP and 2000 before reinstalling:

1. Use Add/Remove Programs from the Control Panel to uninstall Office
XP.

2. Try to use the Add/Remove Programs applet to uninstall Office 2000.
Because of your install history, I'm not sure whether this is going to
be available to you or not.

3. Use the Windows Installer Cleanup Utility, available from this page:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;290301

to clean up any registry settings related to the installation of OXP.
Note that there are two versions of this utility, one for Win98/ME and
one for WinNT/2K. Choose the right one and follow the instructions.

4. Reboot.

5. Look on the Office XP CD for a file called offclean.exe. Run that
utility.

6. (This step may be overkill) Look on the Office *2000* CD for a file
called offclean.exe, and run *that* if you find it.

7. Download and run the Eraser2k utility from

http://support.microsoft.com/default.aspx?scid=kb;EN-US;239938

8. Assuming all this went well, reboot; then reinstall Office XP.
Choose the default
folder for installation, unless you have a good reason to do otherwise.

Dirk...I got'cha ...just... ahmm...having a bit of problem. Seems 2000 does
not want to go quietly into that good night, and won't let go of the root.
Sooo....since it don't want to go...'02 has now copped an attitude...like,
"if it don't go.....then I'm not going either...."
Sheesh....programs.....<sigh>

I'll be back......


Film at a 11:00...as they say. I'll be back......

 

[Dirk Goldgar]

Dirk...I got'cha ...just... ahmm...having a bit of problem. Seems
2000 does not want to go quietly into that good night, and won't let
go of the root. Sooo....since it don't want to go...'02 has now
copped an attitude...like, "if it don't go.....then I'm not going
either...." Sheesh....programs.....<sigh>

I'll be back......


Film at a 11:00...as they say. I'll be back......

Don't let your new governor go to your head. ;-)

I'm going offline now, but I should be able to follow up on this some
time tomorrow -- exactly when will depend on whether the snowstorm here
causes my classes to be cancelled. When I do, I'll want to know exactly
what happened: each step you took and what the result was.

Later ...