Re: Passing variables between packages.

[Quoted] I'm finding this thread logic hard to follow, excuse if i sound thick!

Validation code is just that, why should it make any difference if it is in the form, database package or forms package?

Assuming a WHEN-VALIDATE trigger, if validation done in a DB package, call the function. If 'true' returned to the form, continue processing. If false raise a form_trigger_failure event and pop up your window. After user types in their value in the popup window, write that back to your field. When user tabs off, validation will occur again.

1. Check to see if you are validating twice (ie once in WHEN-VALIDATE-ITEM and once in POST-TEXT-ITEM, POST-CHANGE *heaven forbid!* etc).
2. When the popup window activates, is it being done from inside the WHEN-VALIDATE-ITEM trigger? You cant do this directly since it is a restricted procedure, if it is being done via a timer, i can see the potential for your problems.
3. Is the form being run in client-server or over the web?
4. Try running the form in debug mode and make a note of the triggers being called. May give you a clue as to what is going on.

M

Tim Ashman <tashman_at_attbi.com> wrote in message news:<3CC75CC0.6080405_at_attbi.com>...
> Ok, this might sound like a complete newbie question but I'm not sure
> and my companies application provider has used this as an excuse for why
> a portion of there software package written in developer 6i is working
> differently from their last version.
>
> They use popup windows for adding rows in a table. The scenrio is like
> this.
>
> You enter a value in a field, upon tabbing or mousing off they do
> validation. If the validation fails then a popup window notifies and
> asks if you wish to add this piece of data.
>
> You answer yes and the program will give an error message again stating
> that the value is not valid. They told me that because their code is
> now in a package instead of on the form that the validation cannot be
> "turned" off on the fly, so now we have to backspace or delete the
> entered value, Use the manual popup button to add this piece of data,
> then reenter the value so there form can re-validate it again.
>
> To me, having to enter the same piece of data three times just to add it
> is completely stupid. In there old version with the code included on
> the form this did not happen. They are telling me that this problem is
> hard to fix and they haven't been able to figure it out.
>
> Now before you say, hire new programmers, I know, trust me I know, but
> this is not a mainstream application and even with these types of
> problems it is one of the better ones in this arena.
>
> Any ideas on where to point them. Thanks.
Received on Thu Apr 25 2002 - 15:42:24 CEST