PDA

View Full Version : Constraints again



Bob Worsley
3-Aug-2007, 07:19 AM
I just had a chance to get back to the issue of constraining records as the
Contact Entry example does. (Previous thread on Lookup Constraint) Not
sure if anyone has noticed, but the "Show" radio buttons only work if you
are using the F7/F8/F9 finding buttons, the lookup always shows all users.
Is this by design?

In my application I need the lookup to only show what the radio buttons are
set to. For this one needs an "external" lookup page -- not one of the new
custom dialog lookups so a constraints variable can be passed to the back
end - the variable isn't passed unless also present in the lookup page.
This then brings up the issue of how to pass that variable from the main
page to the lookup... create a cookie? session variable?

I'll work it out, but it seems like a lot of jumping through hoops for what
should be simple. Sorry if I'm beating this to death, but with all of the
other great concepts in the framework, this one IMHO still needs work.
Bob

Harm Wibier
6-Aug-2007, 02:02 AM
Hello Bob,

I don't think this is by design because in the next version the user data is
copied to the automatically generated lookups which causes constrains to
work on lookups either (while the lookup uses the same web object with the
server-side constrain logic).

--
Regards,


Harm Wibier
Data Access Europe B.V.
http://www.dataaccess.nl/


"Bob Worsley" <bworsley@comcast.net> wrote in message
news:mZBafhc1HHA.6020@dacmail.dataaccess.com...
>I just had a chance to get back to the issue of constraining records as the
> Contact Entry example does. (Previous thread on Lookup Constraint) Not
> sure if anyone has noticed, but the "Show" radio buttons only work if you
> are using the F7/F8/F9 finding buttons, the lookup always shows all users.
> Is this by design?
>
> In my application I need the lookup to only show what the radio buttons
> are
> set to. For this one needs an "external" lookup page -- not one of the
> new
> custom dialog lookups so a constraints variable can be passed to the back
> end - the variable isn't passed unless also present in the lookup page.
> This then brings up the issue of how to pass that variable from the main
> page to the lookup... create a cookie? session variable?
>
> I'll work it out, but it seems like a lot of jumping through hoops for
> what
> should be simple. Sorry if I'm beating this to death, but with all of the
> other great concepts in the framework, this one IMHO still needs work.
> Bob
>
>
>