"SingleThreaded" has nothing to do with running multiple instances on the same box. It just means that each instance does use only one main processor-command-pipe. Which isn't even the case with VFP9, which technically uses at least 8 threads already. (see taskmanager/details and add column "Threads")
Each VFP instance is completely isolated from another VFP instance, Windows takes care of separating the memory and address-spaces for each task. You can't just change a memory variable and hope that it would get picked up by another VFP session.
On a higher level, "SingleThreaded" is mostly used as in "this software can only do one job at a time", whereas "multithreaded" often get used as in "does multiple tasks parallel"
In your case I suspect a deadlock at the FoxUser.dbf, which is used by both instances at the same time, since both use the same config.fpw and settings.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox [mailto:profox-bounces@leafe.com] Im Auftrag von mbsoftwaresolutions@mbsoftwaresolutions.com Gesendet: Mittwoch, 6. Dezember 2017 01:00 An: ProFox profox@leafe.com Betreff: 2 VFP sessions running; 1 hangs and so does the other
VFP9SP2 Win7Pro
Had a long running Quickbooks query from VFP (via QODBC tool) take forever. I launched a 2nd instance of VFP to work on something totally different. While editing some code in a PRG, my 2nd VFP session hangs. I leave it, come back HOURS later, still hung. Both VFP sessions. I'm guessing this is because it's single-threaded (although I'll be the first to admit I'm not a threading expert).
Ideas?
Thanks, --Curious in Maryland
[excessive quoting removed by server]