>I'm accessing a database that's actually being used by another program written in FoxPro. My access is read only, no writing is being done, but here's the fun part:- I made a copy of the database to my personal directory on the network to test with while I was programming...I made my SELECT statements, optimized the statements, and it pulled the data quickly...however, when I got done and pointed the program to use the actual database that is used company wide, suddenly all my optimization isn't doing any good...or something, because now a search for a single part number takes 10 seconds instead of 1. It was that much of a perfomance drop...has anyone had any kind of experience with this sort of thing? Any advice?


Just a thought:

If the table is large and there is an index on DELETED() you will experience considersably different response times based on the SET DELETED setting. If it's OFF in development and is ON in the application, this could explain the performance hit. I've stopped indexing on DELETED() because my applications turn deleted ON by default.