Are you sure that the lookup code actually ran the second time? If you have a condition to make sure it only runs once, then it may not have run until you left the record and went back to it.

Erika,

Is it possible that the zip code db was read into memory, and Sesame was using only what was in memory, rather than checking the disk again. And when Spenser closed the app he was working in, and reopened it, that caused Sesame to re-read the zip code db again from disk, which of couse, now contained the new zip code?

Hi -

Mark, You said:

Quote:


I don't understand what you are saying, particularly with regard to the problem I described.

It might help to know that I am using this on my own computer and although it is networked to 3 others none of the were turned on nor is niether Sesame or any of my databases installed on the other computers.  Would I still have a client/server .... or does that just refer to when there is more than one user?

Does the "loophole" you found in the programming mean that it can be "fixed" so that the lookup situation I described won't fail in the future?

Thanks!

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!

Quote:


Have you looked at these?

Quote:

Carl -

I was not familiar with the xlookups you mentioned, so thanks very much for pointing them out.

What I wanted to do specifically - which I understood cannot presently be done - is retrieve multiple values in one lookup statement and have the values entered into appropriate fields.

So, in doing my xlookup based on zip code, I could use one statement to have the city brought back into the city field, the state brought back into the state field ... along with others, e.g. time zone, county or "whatever."

If memory serves me right we could, in Q&A, use one lookup statement and retrieve up to 20 values entered into the appropriate fields.

But Carl,

I care more about me than the computer.

After all, I'm 68 and I always have at least one new computer.

lol