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. Emmitt Dove Manager, DairyPak Business Systems Evergreen Packaging, Inc. [EMAIL PROTECTED] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [EMAIL PROTECTED] From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Sunday, December 07, 2008 2:00 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Running 7.6 code from a batch? Emmitt: This IS running in DOS only, so that's why there's DOS-only commands still in there. We still have about a couple dozen programs we haven't yet upgraded to 7.6 (the really hairy ones). But apparently even when their entire app was in DOS it was probably running slow because of something in this setup file. We have MANOPT OFF as the default. Don't want to mess with setting it on since we have never programmed with that in mind .. Could make more things worse, than things better. I'll have to check if SET SCRATCH TMP was available in DOS 6.5; don't think it was. Yes, the settings are prior to connecting. I don't even know what SORT MAX is! I'll have to read up on it and see if that could be the problem. Thanks for looking! Karen Karen, I’d comment out the SET SORT MAX near the end. I presume that all this is run prior to connecting the database, since several of the commands herein will have no impact if you connect first. I’d also reduce all of the commands relating to scratch to simply this: SET SCRATCH TMP If STATICDB is ON, then I’d also SET FASTLOCK ON. These, too, need to be executed prior to connecting the database. Both require that all users run with the same settings. What about MANOPT? I don’t see it in the list. For certain queries, especially well-constructed multi-table SELECTs, it can speed things tremendously. SET FILES 25 might be a detriment. That’s an old DOS days setting. Depending on what your process is doing, it might be a limitation. RBG7x is going to create more $$$ files than DOS. Try 50 or 60.
