Mark -
I hope at some point, you might be able to look at the situation to see whether there is a "bug" or whether I overlooked something.
If it's any help, here is the programming I am using in the "on element exit" event.
If not @isblank(zip) then
{
Xlookup("C:\sesame\data\ZipCode.db",@left(Zip,5),"ZipCode!Zip Code","City",City)
Xlookup("C:\sesame\data\ZipCode.db",@left(Zip,5),"ZipCode!Zip Code","State",State)
}
if @error then @msgbox("lookup failed","","")
I made sure that I went in and out of the zip code field to trigger the programming, including deleting and reentering the zip code, leaving the record and coming back to it, entering it in another record, etc. etc.
But I can certainly be patient to get your response, since most of us will be THRILLED to have "human" readible/editable macros. (What about the "other" users of Sesame; will they be able to read/edit them also?) roflol (To be very clear, that was just a rhetorical question, in JEST!)
Also, looking at my code reminds me of something else I'm curious about. Will version 2.0 allow us to retrieve multiple values with one xlookup statement (I hope, I hope)?
Thanks!