topic Re: in VBA Forum

OEM and VBA

Anonymous — Wed, 14 Aug 2002 10:23:35 GMT

I have an OEM 2002 application that works on some machines and not on others. There are 4 VBA routines in this application. On some machines, when any of these are run the message "name Execution Error" appears, where name is the name of the routine (VBA macro). I have other machines on which everything works perfectly. These machines are 98, ME, NT, 2000 or XP. All had Office installed before my application. Using one machine that did work, I removed Office (application still worked) and then re-installed both Office and my app (app did not work). ANY ideas? I do not have control over these machines and what goes on them. Thanks.

Re: OEM and VBA

Anonymous — Thu, 15 Aug 2002 07:36:19 GMT

Perhaps you could post the code that creates the
problem.

It might be related to the OS.

Are the ones not working on the same
OS?

What is the error number?

Does it run then crash, or won't load at
all.

style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">

"Pierce" <
href="mailto:triley@piercemfg.com">triley@piercemfg.com> a écrit dans
le message de news:
href="mailto:f103260.-1@WebX.maYIadrTaRb">f103260.-1@WebX.maYIadrTaRb...
I
have an OEM 2002 application that works on some machines and not on others.
There are 4 VBA routines in this application. On some machines, when any of
these are run the message "name Execution Error" appears, where name is the
name of the routine (VBA macro). I have other machines on which everything
works perfectly. These machines are 98, ME, NT, 2000 or XP. All had Office
installed before my application. Using one machine that did work, I removed
Office (application still worked) and then re-installed both Office and my app
(app did not work). ANY ideas? I do not have control over these machines and
what goes on them. Thanks.

Re:

Anonymous — Mon, 19 Aug 2002 10:01:34 GMT

The code is anything, there is nothing specific about the code. All of the machines set up by our in-house technical people work fine, it's the ones that belong to sales representatives. The OS is Windows 98 or 2000.

There is no error number involved. The name of one of these routines is entered at the Command: line and the result is displayed in the text area as "name" Execution Error ("name" is actually the name of the routine entered). The same happens if we enter -vbarun at the Command: line and enter the name of the routine at the Macro Name: line.