>I work for a company that is slowly converting from dBase to VFP, though there are parts of its code that are still being maintained only in dBase.
>
>We have been having a growing number of memory errors, mainly while reindexing. This is in code that I have not started on conversion and would prefer to let wait its turn. I'm hoping someone can suggest a workaround, as my dBase-specific coding skills are 15 years rusty.
>
>When the program hits a spot to create a standalone index (using "TO" instead of "TAG"), it gives a number of bogus error messages (like "File already exists"), but I am told that retrying will eventually yield an "Insufficient memory" error message, specifically related to indexing.
>
>I recall that dBase used the first 640K of memory plus extended memory. The programs as written do not show any settings to maximize memory usage, and I recall that there used to be commands that could be set in the db.config files, or even "SET" commands that do the same thing.
>
>Does anyone remember any such settings?
>
>Is there any other workaround besides converting directly to VFP? They use a couple particular programs to write to an old line printer (!), and I'd like to avoid having to deal with that mess until last possible moment.
>
>Thanks.

Patrick:

The "File already exists" warning when indexing is not a big deal. The .ndx file you are indexing "to" already exists. You can (1) SET SAFETY OFF or (2) erase the .ndx file(s) before the indexing operation. I, unfortunately, have a whole inventory, order entry, accounting system carried over from dBase-IV, to Clipper, then dBase-V that's still running - 20 years later. I keep telling myself that someday I'll convert it to either VFP (still using GET/SAY statements), or something like Recital. I'll probably die telling myself the same thing so long as the programs continue to run -- and they do.

Scott