Well at the moment it sounds as if the design should have been broken up into a series of linked tables early on. Even if it means these are just 1 to 1 relationships.

To avoid making things worse you probably should do this for your new fields (unless someone comes up with a solution to your speed problems).

Even so I am surprised that VFP is not dealing with it well because your record count is not very high.

Are you sure that you have indexes set on all the fields that are involved in your select and that you are using expressions that can be optimised by rushmore?

What sort of PC are you running your select on...does it have enough memory?

have you allocated enough memory to VFP in your config.fpw

There are many factors that you will have to rule out.


I hope some one else can be of more help


>Nope. In can't store as local table. The big one is the main table in a hospital. I'm terrified: I have already 150 fields and I need about 300 more! Things go worse than that: it seems to be about 12000 new records per year...
>
>
>Any ideas?