Comments & OnLookup

Belias

i just noticed that even if there are only comments in the onlookup trigger of a field in a table, the table relation used to look up the table (for example) won't be considered when looking up that field. In other words, in order to not use the onlookup trigger, it is not sufficient to comment out your code, you MUST delete it :shock:

ajhvdb

Yep, the problem with this is, in three months time you forget about this and again, you spend 1 hour finding this out again. for example: try a lookup directly in a table view

garak

a BLANK line is enought to say the System: "Use the lookup trigger". So the trigger should be empty if you won't use it

Belias

fortunately, it never happened to me in 2y of developing...i noticed this while messing with pages and the new lookups...

David_Singleton

Belias wrote:

fortunately, it never happened to me in 2y of developing...i noticed this while messing with pages and the new lookups...

I think this was the first "bug" I reported to PC&C with the new Windows product. After waiting weeks for a reply, the response was "please read the manuals" and yes it does actually state that any code in the trigger will replace the default functionality. So this is a feature, not a bug.

Since then I read the manuals a lot closer and more literally.

Belias

So this is a feature, not a bug

this sounds familiar...
anyway, i can't understand any good reason to make valid blank and commented lines of code...but i can't see the big picture of "god microsoft" :roll:

David_Singleton

The logc was that the program simply looks to see if the trigger is blank, and if blank does its thing. Even a commented line generates something, so that is the trigger to say "Don't perform the default action." Its crazy, but logical in a Danish sort of way.

DenSter

Having any local variables in there will also screw you up.

DenSter

Belias wrote:

but i can't see the big picture of "god microsoft" :roll:

I think that is a bit unfair. It has worked like this since well before Microsoft took over.

Belias

I was joking...you're right ..."these" are not problems...it's only a "strange" thing

garak

I think this was the first "bug" I reported to PC&C with the new Windows product.

that was also my first "bug" report. Long long time ago .....

Belias

damn it! the same happens for OnFindRecord Trigger...but the behaviour is more weird here...nav opens the page but does not show any record...i guess that a line of commented code overwrites the standard behavior (as onlookup trigger does), but the "which" parameter is still blank...
i just wasted nearly an hour #-o

Maria-S

#-o

try a lookup directly in a table view

Exactly!

Just spent about an hour to solve the mystery.
Thank you for mentioning this!