>>This is not a question, it's just in regard to VFP quality...
>>I support high-volume VFP system (1.5 GB, 4 million records in the biggest table) which includes (besides many other functionalities) 'report generator' module to print multiple (5-10K) reports usually as part of nightly batch. These reports essentially data (3-5 pages each) retrieved from multiple high-volume tables using SQL-Select sophisticated chain. The module generates reports into files and then another module moves these files into different printers based on file name and file windows timestamp (to provide right printing sequence).
>>Recently, the module was moved to high-power server (256M RAM) and testing it I saw that sometimes VFP works too fast, i.e. stamps consecutive report files with the same time (the same second) that can mislead printing module. So, I had to 'slow down' the system adding WAIT WINDOW "" timeout 1.0 on start of report routine ::)
>
>Would you like to write a case study on it for the KB article section? I'm sure we can learn a lot from it.

Michel, thank you for your suggestion. Actually, this example doesn't constitute 'case study', it's just brief illustration how powerful VFP system can be for data-intensive situation. I have co-worker here, who wrote VB-SQL Server system for another dept, and we used to run similar queries against similar amount of data, and our VFP was always on top :), and he is really good VB-SQL programmer (btw when we met first time he was sure that foxpro is some obsolete ancient tool).