Re: FORMS and poplists
Date: 1998/02/07
Message-ID: <6bjd6g$7mi_at_bgtnsc03.worldnet.att.net>#1/1
Is this poplist in a multi-record block? If it is, you are toast. Two workarounds are to use an LOV instead of a poplist, and to have a "floating poplist". The poplist is in a separate non-base table block, and it's When-List-Changed trigger copies the value to the appropriate field in the base table block.
Joe Strano
Dulcian, Inc.
Frank W Phillips JR wrote:
> I am attempting to dynamically populate a poplist based on a POST-CHANGE
> trigger attached to another item. When the trigger runs I get a
> "FRM-41331: Could not delete element from list" error. This appears to
> be due to Forms insisting that the poplist have a default value (even if
> it is a blank) when created. Can anyone tell me how to work around this?
> This seems like a standard thing for a database app to do. It is very
> important to my application to be able to build lists based on the value
> of other items on the form. Thanks in advance for any helpā€¦
-- Joe Strano Dulcian, Inc.Received on Sat Feb 07 1998 - 00:00:00 CET