>I tend to do this using shellexecute() but maybe someone else has a better idea? We have some functions that can be run while other processes are ocurring so those are written into separate .exes which are then run as background processes. You really have to be careful though to make sure you separate the processes so both .exes don't try to use the same files (unless that is ok) etc... I recently got an example from Claude Fuchs on using createprocess() to do this which seems to be cleaner and faster than shellexecute() since my understanding is that shellexecute() actuallly calls createprocess().
Well, I was actually thinking about RUN /N, but that is not the main problem. For different reasons, I was thinking of using the same executable again, or of accessing the procedures / classes within it. Otherwise, I would have to duplicate a large part of the class library / procedures for some simple process.
I tried SET PROCEDURE to access the contents of an EXE (compiled from a VFP project), but it doesn't seem to work. Any ideas / comments?
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)