469,920 Members | 2,363 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,920 developers. It's quick & easy.

COM Makepy Question

Using Pythonwin's COM Makepy utility I created a COM wrapper around an
OCX file that's used to communicate with a magstripe card reader. The
wrapper was created without incident and I can invoke any "get" type of
method without a problem. But whenever I attempt to invoke any of the
"set" type of methods I receive an error message that states:

(-2147352567, 'Exception occurred.', (0, 'ctlUSBHID', 'Client
Site not available', None, 1000398, -2146827890), None)

Googling around I see that this error message indicates an ActiveX
control that's being referenced without residing within a container.
Not sure if this is something that I can fix myself within the Makepy
COM wrapper or if I have to rely on the vendor shipping an updated OCX
file. I did see a Python discussion thread where someone else ran into
a similar problem and had to wait for the vendor to ship a revised OCX
file.

Dolphin Smalltalk has a similar COM wrapper utility and the same exact
error occurs. The OCX file is ideally suited for Visual Basic but I
don't have that compilation environment setup on my workstation to try
out.

Anyone familiar with such matters? I have contacted the vendor to try
to initiate things on that end. But if there's something I can do to
circumvent that route using Python I'd give it a go.

Jul 7 '06 #1
0 1005

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Alv Mart | last post: by
3 posts views Thread by Gerson Kurz | last post: by
reply views Thread by Jim Kerr | last post: by
2 posts views Thread by Svenn-Ivar Svendsen | last post: by
1 post views Thread by Tom Willis | last post: by
1 post views Thread by Steve M | last post: by
4 posts views Thread by suzhi18 | last post: by
reply views Thread by Waqarahmed | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.