CASE statement uses equate, not field name

[Jane]

I'm a good shot.

Take aim at foot.  Do not miss 

Yes.  I know.  "Why would you do that?"  "Don't do that."

But I did...

I changed the equate on a form field (just because I don't particularly like the colon-replaced-by-underscores.)

And after a bit of chasing my tail figured out that that's what broke my effort to use a lookup on that field.

The AfterLookup routine grabs the session value for the "lookupfield" - but that's based on the field's equate, not the field name.
Then immediately following is a CASE statement that looks to match the actual field name, not the equate.

Sneaky!

Cheers,

Jane

[Bruce]

sounds like a template bug - I'll fix for the next build.