> the user saved the first time already selected? As opposed
> to returning to the beginning?
Yes, return right away or in the future, no difference in desired
functionality. It is one form with 35 form elements.
> Have you thought about having an optional where statement in
> both queries that only returns one value? So that when the
> user returned to the page the query for A fires and only his
> selected value for A is returned and ditto for B.
This is where the problem lies. The form elements in question are intAgency
and intBureau. The user saved the form initially with intAgency = 1000 and
intBureau = 1011. Now the desired result upon returning to the form would be
for the form to populate with the selected values, including intAgency and
intBureau. However, since intAgency and intBureau are tied to the gateway,
the intAgency field must first be populated before the value can be set...
and, once set, the gateway routines need to run to get the value of
intAgency, pass it into the gateway, returning the values to populate into
intBureau. At that point intBureau can be set.
The biggest problem is trying to find out what specific order the gateway
runs in compared to the rest of the page rendering and also how to control
the gateway to avoid the endless loop I find myself in when trying to take
such control within the predefined methods.
Does all that make better sense? I am confusing myself I think :-)
If I could show you the page, it would be much easier!!!... but its on our
intranet in development. Maybe tomorrow at work I will save the rendered
page and send you a zip file of the files so you can get a better sense of
what in the heck I am trying to do... unless you follow me now.
I appreciate your input... hopefully I find a solution before moving on to
an alternate solution.
Regards,
Mike T.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
