Hai,
I am having a ocx control which acts as a link between two applications AppA
and AppB. The reason for this ocx control was to avoid socket programming in
AppA. This ocx control has socket programming in it. This ocx connects to
AppB through socket programming. The ocx control is included in AppA.
Whenever AppA has to transfer some data to AppB, AppA just calls a method in
the ocx control which transfers the data to AppB through the socket
programming. Whenever AppB has to transfer some data to AppA, the ocx
control receives it, it creates an object and sends the msg to AppA through
a call back function.
This is what the ocx control actually does. The ocx control is working
finely in AppA. AppA and AppB are able to transfer data through this ocx
control. But the exe taken for AppA is not working in any other machine. The
source code is working fine in all machines, but the exe taken in one
machine is not working in all other machines.
I have taken setup for the ocx control and AppA, and run both the setups in
all the machines, but no use.
If I take exe for AppA in Win2000Professional with ServicePack4, VB6 with
ServicePack5, this exe is working on other machines. But If I take exe for
AppA in WinXP, VB6 with ServicePack5, this exe is not working on other
machines.
What may be the issue, is the issue in the setup, or somewhere else? I am
not able to find the solution for many days. The ocx version no. are same in
all the machines. What may be the problem, source is working, but not exe.
Thanks & Regards,
Uma
Dick Grier - 30 Mar 2005 17:25 GMT
Hi,
There may be some dependency (file) that is not included on the machines
where the program is not working. Normally this would cause an error that
is displayed, but...
Dick

Signature
Richard Grier (Microsoft Visual Basic MVP)
See www.hardandsoftware.net for contact information.
Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.
Ken Halter - 30 Mar 2005 18:15 GMT
> Hai,
>
[quoted text clipped - 5 lines]
> Thanks & Regards,
> Uma
What error are you getting? Is the OCX built by you? If so, do you have
Binary Compatibility set? How did you build the setup package?
Most important though, what error are you getting... post the number and
description of the error message.

Signature
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Sign up now to help keep VB support alive - http://classicvb.org/petition
Please keep all discussions in the groups..
Uma - 31 Mar 2005 05:15 GMT
Yes, the ocx was buit by me. Binary compatibitlity is not set in the ocx. I
have built the setup through 'Package and deployment wizard'.
I am not getting any error number, when I double click the exe, nothing is
happening, the form doesn't open, but there is no codings in the form load.
Should I set the binary compatibility, or what should I do?
Regards,
Uma
> > Hai,
> >
[quoted text clipped - 16 lines]
> Sign up now to help keep VB support alive - http://classicvb.org/petition
> Please keep all discussions in the groups..
YYZ - 31 Mar 2005 16:14 GMT
> I am not getting any error number, when I double click the exe, nothing is
> happening, the form doesn't open, but there is no codings in the form
> load.
Add a messagebox in the form_load event and see if that even pops up.
I am taking a stab here, but are you using the Winsock ActiveX Control on
the AcitveX control that you wrote yourself? If so, see if that file
(mswinsck.ocx) exists on the problem machine. If not, copy it over and
register it. See if that helps.
Matt