Dave,

That sounds great for the first half of this problem. I would be grateful if you could post your solution when possible.

Do you have any ideas on how to automate my code for a late binding scenario? I seem to have to re-add this control to my userform every time it is moved.

--
Mark Ivey
"Dave Patrick" wrote in message ...
I don't have it here but this can easily be accomplished. I use a two-line
CMD shell script that uses xcopy in the first line to copy the OCX to the
user's %systemroot%\system32 directory then use regsvr32.exe on the second
line to register the control as part of a small Access/Excel installation
routine.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Mark Ivey" wrote:
Has anyone ever dealt with the MSCOMM32.OCX control via MS Excel?

I have an application I build recently, but I would like to automate it a
bit. Every time I transfer the file from one PC to another, it takes a bit
of time to set up. Does anyone have any experience with this type of
automation?

The big problems are as follows:

Usually I have to make sure the PC it is going on has the MSCOMM32 file and
that it is registered with Windows.

Once that pain-staking task has taken place I have to add the MSCOMM
controls back to my userform.

After doing this all seems to be okay, but some of the items above can be
difficult on some PCs.

Can this type of thing be packaged and or automated?

--
Mark Ivey