Kirby at wallaceinfo dot com
|
| Posted: 03/08/2002, 1:20 PM |
|
It would be nice of the BEFORE UPDATE event fired BEFORE the Update SQL String is CONSTRUCTED. This would give me time to adjust individual fields just before they are written.
As is:
1. SQL="UPDATE blah SET fldBLAH1=jfse, fldBLAH2=cchfd"
2. fldBLAH1="NEW VALUE"
3. EXECUTE sql
NEW VALUE IS LOST because the string was constructed first and then the before update event set NEW VALUE.
|
|
|
 |
Steve Mol
|
| Posted: 03/08/2002, 6:54 PM |
|
I'll second that -- and add a bit more.
I'd like a BEFORE SEARCH event on the Search screen. For example, I have a telephone call duration field in the database that is stored in seconds. On the Grid form, in the BEFORE SHOW event, I run a function that converts the seconds to a minutes/seconds format (ie, 72 becomes 1:12). On my Search screen, I have "Minimum Duration" and "Maximum Duration" fields. I would like to allow the user to enter 72 seconds as either 72 or 1:12. In order to do that, I need to run a function against the field before the SQL string is generated. The function is easy, but there's no event to put it in.
|
|
|
|
cornwell
|
| Posted: 03/09/2002, 7:14 PM |
|
The help file says 2.04 ....
BEFORE UPDATE: Executed before updating records in the database.
Often used to modify the SQL query or the data.
You may use sSQL, fld<field_name>, s<Form_Name>Err variables
...end
Which is ambiguous. It says " ...or the data", which is false. Using a fldxxx variable is not taken into account.
I vote for the request too.
|
|
|
|
D Newman
|
| Posted: 03/10/2002, 11:50 PM |
|
Is it not possible to put these items into the form validation?
|
|
|
|
|
