>>>As the others replied it will work. But if you ONLY want to call it from vfp and not from other COM-aware programs I'd recommend splitting up your exe into app's - same modularity, higher speed (becaus no marshalling is needed) esp. if you call a method "from the other side" very often or with many parameters, less deployment issues (no registration!).
>>>
>
>>Thanks for the heads up Thomas. This sounds like the way for me to go. Are there any other issues that you are aware of that I should consider with this approach?
>
>Depends how large and interconnected your app is. Having inheritance chains across multiple app's takes a bit of thought or you run the danger of having duplicate code in the apps. Having vcx's in the exe is no problem, but factoring out "middle parts of inheritance" needs those apps to be already opened for troublefree work. Did that a few years ago on a large app, cutting down double- and triple linked code (on the order of 12 MB) and had to implement a scheme to open app's via small utitity functions for certain modules. Depends much on your code <g>.
>
>regards
>
>thomas

Well I'm stumped already. I compiled a bunch of functions and procedures into an exe as a test. I tried to call a procedure using DO myProc IN myTest.exe WITH 1. While this worked from the command window (i.e., no crash or errors), my problem is that the procedure is supposed to return a string. How do I get the returned value with a DO ... IN ... syntax?

Mike