TechResearch
Programmer
when I call from Visual Basic a method exposed in a dll (COM object, created with Visual C++) sometimes the method takes a lot of time to return the value. Is there a way to report back to the application after some time has elapsed so all the programing control does not rests on the dll. (So the user knows something is happening behind the scenes and the application is not frozen)