MDE suddenly not working on Windows Vista PC

A pc that was created in MS office xp's Access 2002 has been working fine on
a windows vista Ultimate pc that has MS OFfice Vista Edition. But all of
the sudden it stopped working and gives this error, when a button is
pressed. The button launches procedures to download and parse XML files.

This error occurs when an event has failed to run because Microsoft Office
Access cannot evaluate the location of the logic for the event. For example,
if the OnOpen property of a form is set to =[Field], this error occurs
because Access expects a macro or event name to run when the event is fired.

But on the xp machine where the machine is made compiled and saved as mde,
the mde has no errors and compiles fine. I tried to compact and repair, but
still doesnt work. I should note that the app works fine on XP machines and
was working on the Vista machine until recently. No changes made to the pc
other than the automatic updates, so I am assuming a recent update from
microsoft is causing this.
maybe something to do with the xml driver. the mde is using msxml version
4.

Can anybody help?

Thanks

Ardin

Re: MDE suddenly not working on Windows Vista PC

You might have to move an .mdb copy to the machine giving you trouble, so
that you can open a module and check the tools, references section. If you
find any references that are missing, that will point to the problem.

Just an idea, not sure if this is it at all...

"mindspring" wrote in message
news:13it2e27fa0hb0d@corp.supernews.com...
>A pc that was created in MS office xp's Access 2002 has been working fine
>on a windows vista Ultimate pc that has MS OFfice Vista Edition. But all
>of the sudden it stopped working and gives this error, when a button is
>pressed. The button launches procedures to download and parse XML files.
>
> This error occurs when an event has failed to run because Microsoft Office
> Access cannot evaluate the location of the logic for the event. For
> example, if the OnOpen property of a form is set to =[Field], this error
> occurs because Access expects a macro or event name to run when the event
> is fired.
>
> But on the xp machine where the machine is made compiled and saved as mde,
> the mde has no errors and compiles fine. I tried to compact and repair,
> but still doesnt work. I should note that the app works fine on XP
> machines and was working on the Vista machine until recently. No changes
> made to the pc other than the automatic updates, so I am assuming a recent
> update from microsoft is causing this.
> maybe something to do with the xml driver. the mde is using msxml version
> 4.
>
> Can anybody help?
>
> Thanks
>
> Ardin
>
>
>
>

Re: MDE suddenly not working on Windows Vista PC

On Nov 4, 10:10 pm, "mindspring" wrote:
> A pc that was created in MS office xp's Access 2002 has been working fine on
> a windows vista Ultimate pc that has MS OFfice Vista Edition. But all of
> the sudden it stopped working and gives this error, when a button is
> pressed. The button launches procedures to download and parse XML files.
>
> This error occurs when an event has failed to run because Microsoft Office
> Access cannot evaluate the location of the logic for the event. For example,
> if the OnOpen property of a form is set to =[Field], this error occurs
> because Access expects a macro or event name to run when the event is fired.
>
> But on the xp machine where the machine is made compiled and saved as mde,
> the mde has no errors and compiles fine. I tried to compact and repair, but
> still doesnt work. I should note that the app works fine on XP machines and
> was working on the Vista machine until recently. No changes made to the pc
> other than the automatic updates, so I am assuming a recent update from
> microsoft is causing this.
> maybe something to do with the xml driver. the mde is using msxml version
> 4.
>
> Can anybody help?
>
> Thanks
>
> Ardin

Do you have ADOX as a library? Vista includes a newer version of ADOX
which requires a new build on Vista to use it. The library references
say it's not broken, but it is. The result is the use of VBA
functions, etc. in your queries fail.

Luke Chung
President
FMS, Inc.
http://www.fmsinc.com