>I have a requirement to generate data from VFP for a scheduling process written in VB. The VFP program must ask the user for some information to determine the type of information to send back. The VFP program needs to be a .DLL rather than an .EXE so that the VB program will wait for the VFP process to complete before resuming execution.

It seems to me that in this situation, it would be more natural to have to VB process ask the User for parameters and then pass those on to the VFP program, via remote automation or even a file/table. If the User has the option to cancel, then the VFP program does not even have to be called.