USB/COM Port problem

[judgeh59]

I'm attempting to get a scale to input data into Excel using VBA(hopefully). The scale has a USB interface and I have setup the interface according to docs (I believe). The port that gets created is COM5. I have done the port setup on that also. I set up the scale to send data when the reading is "Stable" and the print button is pressed. Nothing happens. I get the impression from different websites that I should be able to program this. I saw MSComm in a different forum and I believe it's only in VB5/6 and I don't have access to that. I checked the VBA object library and searched for MSComm and came up empty. I haven't started any code because I'm new at the whole open hardware stuff...any help would be greatly appreciated. thanks.

Be Alert, America needs more lerts

 

[Gruuuu]

It looks like the file (mscomm32.ocx) is not included with Windows Vista. It can be downloaded, but then has to be distributed with your file. I do not know how this is done, but here, have fun.

http://support.microsoft.com/kb/957924/

 

[judgeh59]

thanks Gruuu....a couple of things...I'm using XP Pro not Vista...that link is for VB and I'm not running VB just VBA....I don't have access to VB5/6. I couldn't see anywhere on the MS site to just get the MSComm out of the VB update file...I didn't check but I believe I can download the cab and extract just the mscomm....but I'll have to do more digging....thanks...

Be Alert, America needs more lerts

 

[Gruuuu]

Yeah, that was my assumption on the installer, was that it just had a package of files.

If you can get that file out of there, though, you can register the DLL (or OCX) from inside your project and hopefully access the references.

 

[strongm]

mscomm32.ocx is indeed redistributable - but not with a developer license, I'm afraid

 

[judgeh59]

thanks gentlemen...I have got the reference in to VBA and that's half the battle and I'll start coding...I'll worry about the reditribution later....thanks again...

Be Alert, America needs more lerts

 

[strongm]

>I have got the reference in to VBA

And will be breaching license terms if you use it to develop a solution ... that was part of my point.

 

[judgeh59]

strongm --- thanks and understood...is there a solution beside purchasing the big expensive license?...I'm not willing to do anything illegal...this will be for a production line so I want everything above board...I just don't know all the rules...thanks

Be Alert, America needs more lerts

 

[Gruuuu]

I am a third-party software developer, and I use the ActiveX controls in my application. What do I have to do?
If you redistribute the ActiveX controls, make sure that you update the version of the ActiveX controls that are installed together with your application by downloading this cumulative update rollup. For more information about the best practices for using redistributed components, click the following article number to view the article in the Microsoft Knowledge Base:

http://support.microsoft.com/kb/835322/

835322
Applications that bypass globally serviced side-by-side assemblies may be vulnerable to issues that are fixed by a Microsoft software update

Are we sure this is a licencing issue?

 

[strongm]

>Are we sure this is a licencing issue?

Yes. We are. If you have a design-time license for an ActiveX control (e.g with Visual Studio) you can develop an application that uses that control. If it is a redistributable control, you can redistribute that control with your application with a run-time license so that the end user can use your control. You cannot redistribute the design-time license ...

 

[judgeh59]

thanks guys - I really do appreciate the help and I would error on the side of right. I work for a fairly large company and I don't want to put them in "an awkward position"....that being said, strongm - is there a work around?...legally...I don't have VB5/6/studio....all I have is office2003 license systems...can I do anything without breaking the law?....thanks again....

Be Alert, America needs more lerts

 

[strongm]

I am afraid that I am not aware of a legal workaround other than having a properly licensed copy of Visual Studio