Thanks, Troy, that's a mature elaboration of what I think I was thinking.
Lemme' ask you another related Q.

I'd like f/my users to be able to leave the Field/Row when they press
[Enter], i.e. no confirmation, as this is high-volume and high-speed data
entry as well as the fact that I'll be doing the VALIDATION and SKIP
processing through code.  So, would you recommend a Key Map?  Would [Enter]
be re-mappable at all?  Other thoughts?

Thanks,
Steve in Memphis

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Troy Sosamon
> Sent: Monday, March 18, 2002 12:15 PM
> To: [EMAIL PROTECTED]
> Subject: RE: RB6.5++ Functional Equivalent to Older RB Versions of
> VARIABLE Forms (or Other Ideas)
>
>
> Steve,
>
> A couple of things you might want to think about doing:
>
> 1. Consider using the INSERT command and inserting the row and
> then edit it
> with your form instead of ENTER USING.
>
> 2. Use the old fashioned variable forms, but the new versions of R:base
> don't support variable forms so you need to use a trick.  Make a
> dummy table
> and put 1 row of data in it.  Make a form that drives off of the dummy
> table.  Before you call the form, use a cursor or select or
> whatever method
> and load all of the data you need into variables.  Now go put the
> variables
> on your form that runs off the dummy table.  When you leave the form, ask
> the user if they want to save their changes and then update your data.
> Don't forget to check the sys_rowver column to check for concurrency
> control.
>
> This is quite a bit of work, but it is a good way to get a lot of control.
>
> Troy Sosamon
>
>
> ===== Original Message from [EMAIL PROTECTED] at 3/18/02 10:46 am
> >F/those of you who read my last missive,
> >"Forms.Region.Tiered.NEXTROW.INTENSITY => Navigation Problem", I'm asking
> >about a work-around.  I've set up a SCROLLable CURSOR approach
> to this, but
> >I'm having some trouble using "ENTER USING ... FOR 1 ROW" when
> it only has a
> >VARIABLE Field on it, albeit one that is enabled for "New Data"
> and "Change
> >Data".  Does anyone have any ideas about this?
> >
> >If not, any thoughts on locating a COLUMN-based Field on a Form.
>  What I'm
> >trying to do is navigate through a pre-defined sequence of records, doing
> >data-entry, processing validity checks, skips, etc, based on that
> >pre-defined sequence.  If it helps, this is related to survey-based
> >research.  And please, no references to SubmitThis, WinCATI,
> web-enablement,
> >etc, as I'm working on what I think is (somewhat) better
> approach to this,
> >that is a data-centric system based on a good data model, rather than
> >code-centric, ad-hoc, one-off approaches which offer limited re-use and,
> >therefore, limited payback.
> >
> >Anyway, thanks,
> >Steve in Memphis
> >
> >================================================
> >TO SEE MESSAGE POSTING GUIDELINES:
> >Send a plain text email to [EMAIL PROTECTED]
> >In the message body, put just two words: INTRO rbase-l
> >================================================
> >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> >In the message body, put just two words: UNSUBSCRIBE rbase-l
> >================================================
> >TO SEARCH ARCHIVES:
> >http://www.mail-archive.com/rbase-l%40sonetmail.com/
>
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
>

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to