there is another solution not so efficient that the one you want but a lot more
simpler.
The first time a table is needed for lookup, you download it in the datasession
n°1 (for example). I do this using a class with a child class for each table.
Using pemstatus( ,5) I can chek if the child class has been instanciated and the
table downloaded.
When you need the table in another datasession, you use the clause NOREQUERY 1
of the command USE :
NOREQUERY [nDataSessionNumber]
Specifies that data from a remote SQL view is not downloaded again.
NOREQUERY is available only for SQL views and is typically used when you
open a SQL view again by including the AGAIN clause. Including the NOREQUERY
clause increases performance for large data sets because the data does not
need to be downloaded again.
nDataSessionNumber can be included to specify that data for a remote SQL
view in a specific data session isn't downloaded again. If
nDataSessionNumber is omitted, data isn't downloaded for the view open in
the current data session.
HTH
The Foxil
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/55a96259.30...@wanadoo.fr
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
