hi Johan,
>> I have 20 fields that must use the same Lookup procedure, each field have a different "type" value that the lookup browse must filter on before opening the browse.
ok, but anything you want passed there must be added to the button when the window is generated. (As far as I can see there's no obvious template option to pass a parameter to the lookup procedure, which may make things tricky for you.)
the button is in the browser. Not on the server. So when you click on the button, code runs in the browser, not on the server. That code opens the lookup window.
>> In Routines- CallDiv- Selected Event, IF I add code in this embed point, then nothing happens. What is this embed point used for?
to notify the server when the user selects an entry field in a form. It serves no use for a button.
>> When I add in the next embeed point - Accepted Event- it works but first bring the lookup browser up,
yes, like I say, the lookup is opened by the browser. (The lookup procedure is always there on the page, it's just hidden')
>> select and after closing the browser, the stop happens.
correct - there's no embed to do what you want because what you are looking at does not happen on the server. The only way this works is if a "parameter" is added to the lookup button (something not currently in the template.) That can be added to the list of things to do.
Cheers
Bruce