Yes, you can speed up the XLookup - without making it internal. Using an external XLookup, you can put an XLookup in the GLOBAL CODE section. It will run when the form is opened. It can even be a "bad" Xlookup, using an non-existent LE name in the key field. Just make sure it uses the same .db file as the "real" XLookup that will run later. Then, put the "real" XLookup in the event where it is really supposed to go.

The XLookup in GLOBAL CODE will run first, so the form will take a few moments to open, but subsequent XLookups to the same .db file will be much much faster.

In general, the first XLookup to any .db file will be slow. Subsequent XLookups will be as fast as internal XLookups. So this technique works by moving the first XLookup "out of the way".

This applies to any of the "X" commands.

As an example, try this in Customers.db:

------------------------------------
in GLOBAL CODE:

var str as string

str = @XLookup("c:\Sesame\Data\Samples\ZipCode.db", "Hiram", "xxxxxCity", "Zip Code")
writeln(str)

------------------------------------
in Company ON EXIT

var str as string

str = @XLookup("c:\Sesame\Data\Samples\ZipCode.db", "Hiram", "City", "Zip Code")
writeln(str)

------------------------------------

The XLookup in in GLOBAL CODE will run just before the form opens, effectively "internalizing" the ZipCode.db. Then when you exit the Company LE, the second XLookup will run nearly instanteously.

Well, that leads to something new!! Yes, declaration of stat variable is at the top of other code.  I also have other subroutines and functions in the GlobalCode.  If I put the statement part before any of the subroutines, it throws out errors. If I put the statement part at the end, after all subroutines and functions, it does not cause any error.