Re: RE: RE: Suppress Add
Hi Bill,
I also certainly wouldn't want to argue with you
but maybe I do with the documentation.
At first, on Header and Headerless Detail forms I can update and delete records as well as add records in update mode.
My questions are (not to you but to the author of the documentation):
1.) How can I handle added and updated records separately without adding work columns and special ER logic to the form to distinquish the added and modified records?
2.) Why does "Add Grid Record to DB - Before ER" (and the other ADD events) have functionality in add mode and does not have in update mode?
3.) Why to handle added records in the Update (instead of Add) events in update mode while I can handle delete records in the Delete events?
4.) Which is the true, the Appendix B or the On-Line help?
I always see SuppressAdd calls in the Add Before event where OW handles the data with Master Business Functions. In these case, the record update and record delete are also suppressed the same way with the appropriate SysFunc calls in the related events as well as record addition. Could it be possible that the SuppressUpdate SysFunc call in the Update Before event will prevent the record addition in Update Mode while the SuppressAdd SysFunc call in the Add Before event will do it in Add Mode??????????? Does it have any sense?????
Now I am really very curious to the truth without creating junk data and junk applications to experiment it myself!
At last, let me copy the "Add Grid Record to DB - Before ER" event topic here from the OneWorld On-Line Help.
===========================Copy Starts================================
Add Grid Record to DB - Before
Description
Event Rules attached to this event occur after you press OK to add a grid line record to the database, but before the record is actually added.
Available On
Headerless/Detail
Header/Detail
Available Objects
All objects are available. However, values have already been propagated into the BC’s so those are the ones that should be modified to affect the record in the database.
Typical Usage
Use this when you want the behavior to affect the saved record. For example, use it to time-stamp a record entered from the grid into the database.
If no records are to be added, use the SuppressAdd business function.
Additional Notes
This event differs from the corresponding event, UpdateGridRecordtoDB, because the attached behavior occurs relative to the addition of a new record to the database.
Processing Sequence
The BC’s are set up just as they are to be added to database.
Run Add Grid Record to DB - Before.
J. D. Edwards Standards
This event works with grid records only. To work with form records use the corresponding form events.
===========================Copy Ends==================================
Please, read attentively the "Additional Notes" paragraph.
Regards,
Zoltán
B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)