Client application using remote ActiveX component - early vs. late bnd

[yen]

I am currently developing a client application to work with a remote ActiveX component. Both client app and server component developed were in Visual Basic 6, Enterprise Edition. Everything works fine using late binding.<br>
<br>
However, we want to use early binding because we forsee passing UDTs. Using early binding, the object is correctly instatiated on the server machine and seems to be sending information back to the client machine. Then, the client machine bombs. The error is:<br>
<br>
Instruction at &quot;0x00000000&quot; referenced memory at &quot;0x00000000.&quot; The memory could not be &quot;read.&quot;<br>
<br>
Any ideas about what the problem is would be greatly appreciated.

 

[pdwetz]

We ran into a related problem on our project. We use MTS to handle our remote components, but our solution may help anyway. It consisted of using early binding during development, and then late binding for our remote clients. This allowed our programmers to use the benefits of early binding, while making our app distribution simpler (not too mention smaller).<br>
<br>
The client uses a shared INI file from our network file server to look up the class id's for the components.<br>
<br>
I'm not sure if this helps or not, but at least it may point you in the right direction.