EDIT USING is definitely a better way to go, especially now with the great PROPERTY commands, it gives you a much better way of controlling the data input process. Mark
-----Original Message-----
From: [email protected] on behalf of Emmitt Dove
Sent: Mon 5/2/2005 12:43 PM
To: RBG7-L Mailing List
Cc:
Subject: [RBG7-L] - RE: EEP's in a scrolling region
Mark,
I can't give you a good reason for the background, but indeed all of the
forms in our application (over 500 of them) are used in EDIT mode. I
guess
it goes back to the old DOS days where our forms contained only
variables,
not fields, and all the control was done in eeps. Some may have seen
this
as inefficient, but I enjoyed the control. So the 'edit using' carried
over into 7.x, and it still holds true that every row that gets inserted
into a table is done so by our code, even from EDIT USING forms. (Hint:
the dummy table gets a real workout! (but still contains only one row
...))
>I actually tried that and it does not work when you use the form
>in 'ENTRY' mode, however it does work in 'EDIT' mode, so I may just
have
>to re-write my code and use the form in EDIT mode. Thank you for your
help.
>
>Mark
>
> -----Original Message-----
> From: [email protected] on behalf of Emmitt Dove
> Sent: Sat 4/30/2005 8:07 AM
> To: RBG7-L Mailing List
> Cc:
> Subject: [RBG7-L] - RE: EEP's in a scrolling region
>
>
>
> Mark,
>
> Also possible:
>
> DBEdit A accepts scan and has on-exit eep for validation
> DBEdit B (hidden behind A) has on-entry eep that does SAVEROW,
> inserts a
> new row and then NEXTROW with a PROPERTY command to SET_FOCUS
on the
> desired field.
>
Emmitt Dove
Manager, DairyPak Business Systems
Blue Ridge Paper Products, Inc.
40 Lindeman Drive
Trumbull, CT 06611
(203) 673-2231
[EMAIL PROTECTED]
[EMAIL PROTECTED]
<<winmail.dat>>
