>>Hi everyone,
>>
>>My colleague suggested to put our small lookups table content into memory, which would speed up the Database validation job. How this could be done?
>>
>>Thanks in advance.
>
>Nadya, making cursors looks like a reasonable way to put them in memory.
>
>Something that I do when I have to "decode" content is to make arrays, lets say, I have x orders statuses, 1 = "Paid in full", 2 = "Not paid", etc.
>In my orders table I store the digit, when is time to report or to show in a form all I need to do is to create an array aOrdStat and then show/print aOrdStat[digit].
>
>Additionally, VFPs has caching habilities not so well explained to us, so it is possible that after the first access, those small tables get cached and then you have them already in memory...

So, do you suggest to select code from LookupTable into cursor curLookupTable
index on code tag code for all lookup tables in order to put them into memory?
Do you think, it would speed up the process?