Hi Christian,

Guessing that the array is being filled with more than 65,000 items.

You say that the files are not corrupted.

Is it possible that the tables have been "modified" by the distant user - either the data itself (themselves?) or the indexes?

Is it possible that the application runs with lots of Deleted() records in the relevant tables and that the distant user has switched things to now be run with DELETED OFF? (. . . or removed "FOR NOT DELETED()" from index definitions?)

Is it possible that the distant user has switched to a different machine with smaller RAM?

Is it FP(DOS) or FP(Windows)?

I suppose there could be many reasons BUT all that I can think of would be the result of some change(s) at the user end.

Good luck,

JimN

>Hello,
>
>In one of our FoxPro 2.6 applications, suddenly an error occurs "SQL out of memory", having to do with SQL's into ARRAY.
>This error occurs on several places in the program that are not related to each other but that all do SQL's into arrays (as far as I can tell).
>
>The results of the SQL's are all small.
>The program where this problem occurs is installed in another country, so I do not know where to look first and I cannot travel there without having a clue first of what could be the reason.
>
>The FoxPro library file is updated to 2.6a.
>The same application runs on other places with similar data without problems. Files are not corrupted.
>
>What else can cause this error?
>
>Thanks for your help in advance.