>I am running FP 2.5 DOS and connecting to SQL Server 4.2 using FPSQL.PLB. Under WFW 3.11 everything is fine. Under Win 95 I cannot execute the RUN/! command after connecting to SQL using the
>DBCONNECT() command. I get the message "RUN/! Command failed". Everthing is fine until I issue the DBCONNECT() command, COMSPEC and everything else is fine. Any Ideas?
Depending on what you are trying to do, in Win95 you could
Run Start
instead, so you don't shell out (obviously your dbconnection is eating up your task's DOS memory), but spawn a new thread instead, which should receive its own memory space (still sharing the DOS part, sorry). The disadvantage is that you'll probably never know what happened in that thread, unless it makes/updates some files and your FPD can check for them before resuming.
I've tried running two instances of FPD2.6X from each other. The second instance feels the 79K that the first instance took; running !mem /c/p from it shows it actually twice, i.e. each task took its chunk of DOS memory. The first instance resumed even before the other instance became visible - the spawned process returned controll to its master and continued in its own thread. The first process also saw twice the 79 K occupied. As far as this checking goes, it seems to behave the way I described it. HTH
