My COM Object is an ATL In-Proc DLL server. From the Client App I created the COM object and get the Interface pointer using CoCreateInstance. I then pass this interface pointer to a worker thread by marshaling the pointer using AtlMarshalPtrInproc and unmarshal the interface pointer in the worker thread using AtlUnmarshalPtr. So far It only works OK on Windows NT but not Windows 95 both version A and OSR2. I've not compiled and registered the Proxy-Stub DLL generated by the MIDL compiler. Is it nescessary to use this proxy-stub DLL when you need to marshal the interface pointer and when is it a must to use this DLL??
This really depends on your interface. If your interface is a dual or automation interface, then the regular automation marshaller should be able to take care of marshalling the interface between apartments.
MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.
Database storage, where is the exe actually on the disc? Playing a game selected randomly (how to generate random numbers). Error trapping with try..catch to help the code run even if something goes wrong.
Continuing from the seve…
Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel.
Part 1 of this series discussed basic error handling code using VBA.