>>>>>>Do you think it would work well running two instances of an EXE to test for record contentions and locking, etc?
>>>>>
>>>>>For that it's simpler to just run two EXEs (or two instances of VFP) on the same OS....
>>>>>Regards,
>>>>>Viv
>>>>
>>>>We need to be able to check over a network and I thought that VM might provide that, but it looks like not.
>>>
>>>Viv is right. You can run more than one instance of the exe in a single host OR a single vm with your database on a network, or not.
>>
>>I was hoping to emulate a true multi-user network environment on the laptop. That does not look like an option.
>
>Someone already mentioned this but I have had good luck with a simple approach: running two EXEs at the same time under the Windows that's already running, no virtual machines. Since each user of a networked VFP application is already running his own instance, the main issues that need to be tested are table and database contention issues. This is easy to create by running the EXEs from the VFP debug environment and setting a breakpoint where the app does a read or an update. Start one VFP session, let the app run to the breakpoint, then run the second session using the same form(s), table(s), and record(s).

I've found that works well, too. About all you have to do is make sure you set up separate FOXUSER.* files and any other environment files/settings in use by each VFP or EXE instance.