1.
http://www.vbaccelerator.com/insprob.htm
2. On one of the non-development computers, create a new VBA project and try
to add that particular component. If you get an error like "the control
could not be created because it is not properly licensed" then you have a
different level of license on your development PC for that ActiveX due to
the VS installation.
2a. Installing VS might help the other PCs run your code. Uninstalling
VS on those PCs may or may not break it again. Only install what you have
licenses for, or, if you only need to run on a few PCs within your control,
consider installing one of the (free) 'express' versions of VS.NET on those
PCs and see if it gets you the target component and license permission
level.
2b. If you need to distribute your workbook more widely, you may have to
determine if you can wrap some of your code into a VS.Net program and
(reviewing to make sure you are within the license agreement) distribute it
along with your workbook. That way only your VS.Net code would call the
ActiveX; your VBA code would call your VS.Net code
HTH,
Keith
KC said:
No this is a fairly simple macro. Nothing shows up as missing in the
references. The big difference between the three computers that i am
using
is that the development computer has visual studio on it and the two that
get
the run time error don't. I have been told to load visual studio and then
uninstall it and then the MScomm.ocx ActiveX component will work. I am
trying to avoid this if i can.
--
KC
Dave Patrick said:
The line of code it stops on can be misleading. Tools|References and look
for something not required or marked as MISSING
Could be something like a datetime picker, calendar control.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
KC said:
in excel i am referencing the MSComm 6.0 axtive X control in a macro.
and
it
works on my computer. I get the "Run-time error 429: ActiveX comonent
can't
create object" when i run the macro on another computer at the line
"Set MSComm1 = New MSComm". The activex component has been registered
on
the computer. What else should i try? I am using Excel 2003 on all of
the
computers.
