General information
Category:
Windows API functions
Hi All
I'm baffled at the logic, which seems to have been forced, behind COM+ and DCOM. COM works as packaged, Local objects created on Local machines/servers. DCOM, on the other hand, is Remote Objects created on Remote machines/servers over a network.
That said, why should you have to install the object locally when it will only ever be created Remotely on a server?
There are way around it, as I'm discovering with my latest project, DCOMAnywhere. Using CoCreateInstanceEx() in Windows API, you can do a remote invocation for an object which has not been installed locally, just on the server.
I'm doing this in VFP7 as we have a massive callcentre here and have an in-house console built in Fox and it would be good to have it useable globally. There are problems with coding as fox isn't that good at strong-typing and has holes in its list of variable types etc.
Has anyopne else had any use of CoCreateInstanceEx(), OleInitialize() or CoInitializeEx() in any language, but Fox especially? Parameters for the above seem tricky for me at the moment
any help would be cool
cheers
Tim Hustler
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only