Karen, Does the program run slower in windows if the set file is run? If not, It is probably just the better memory management in windows. You can set up RBWIN to run from a batch file the same way you can with RBDOS. Why not just do that?
Dennis ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, December 08, 2008 8:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Running 7.6 code from a batch? Emmitt: MY point is that this file is NOT run in Windows. I've said it a bunch of times. It is run only in 6.5 DOS. I have traced the program in Windows just for the heck of it to see if there's any errors, and there isn't, but it is NEVER run in windows. That was our clue when the same program, which can be run from windows and from DOS, runs 10 times faster in windows and we were wondering why. That's what pointed us to the fact that DOS runs this offending setup file. Karen Karen, The point to be made here is that there are some DOS settings that may well hamper Windows execution. The file could include some tests to see if it is running in Windows or DOS (get (CVAL('VERSION')) then parse for the word "Windows") and decide how to set things. SCRATCH is one of those settings. So: SET VAR vversion TEXT = (CVAL('VERSION')) IF vversion CONTAINS 'Windows' THEN SET SCRATCH TMP ELSE SET SCRATCH ON ENDIF Both bases are covered. MANOPT shouldn't be considered a global setting, but rather applied when appropriate. It can make a huge difference in query execution times, especially when the programmer understands the table relationships well and structures the query most efficiently, and most especially when the database hasn't been rebuilt recently so as to refresh index statistics. You can prove this to yourself by finding a particularly slow query and timing it both ways.
