Re: Forms4.5 HELP !!!
From: Tilen Skraba <skraba_at_zav-mb.si>
Date: 1997/11/05
Message-ID: <878744242.11491_at_dejanews.com>#1/1
> We've a very simple forms 4.5 application (10 fields). ID and SPECIES
> fields cannot be null. I've a trigger on both fields to make certain
> that neither are null.. When I enter the form my first enterable
> field is ID and the cursor is placed there. If I click anywhere
> prior to entering the ID I receive an error (that I must enter ID) as
> I should. However, after I've entered ID if I use my mouse to skip
> over the SPECIES field I don't get a similar error unless I've first
> entered the SPECIES field. I've tried using each of the WHEN-MOUSE...
> triggers to no avail. I do have a pre-insert/update trigger that
> checks that both fields are not null & these do prevent commiting bad
> data to the database. I would, however, like to write a trigger to
> immediately inform the user that SPECIES cannot be null whenever
> they've used a mouse to skip over the field. Any solution?
Date: 1997/11/05
Message-ID: <878744242.11491_at_dejanews.com>#1/1
Hello!
Why don't you disable all other fields until all your conditions are met. The items will be grayed out and not navigable by mouse and keyboard.
In your case: Set "enabled" property to false for the other 8 fields. (in a designer) Write When-Validate trigger on SPECIES, which sets "enabled" property to this 8 fields to true.
You can set properties of an item with Set_Item_Property command.
I hope, this helps you.
Sorry for any mistakes in english.
In article <345f7853.111027789_at_news.services.fccc.edu>, am_balshem_at_fccc.edu (Andrew M. Balshem) wrote:
>
> We've a very simple forms 4.5 application (10 fields). ID and SPECIES
> fields cannot be null. I've a trigger on both fields to make certain
> that neither are null.. When I enter the form my first enterable
> field is ID and the cursor is placed there. If I click anywhere
> prior to entering the ID I receive an error (that I must enter ID) as
> I should. However, after I've entered ID if I use my mouse to skip
> over the SPECIES field I don't get a similar error unless I've first
> entered the SPECIES field. I've tried using each of the WHEN-MOUSE...
> triggers to no avail. I do have a pre-insert/update trigger that
> checks that both fields are not null & these do prevent commiting bad
> data to the database. I would, however, like to write a trigger to
> immediately inform the user that SPECIES cannot be null whenever
> they've used a mouse to skip over the field. Any solution?
-------------------==== Posted via Deja News ====-----------------------
http://www.dejanews.com/ Search, Read, Post to Usenet
Received on Wed Nov 05 1997 - 00:00:00 CET