Alastair 

Good points. I guess this is where a lot of the times I don't have the time
to really do things like it should be done. With handling networking, pc
support, programming, and database work for several companies all at once I
often try to pound things out in a hurry, and then if something doesn't 
work as happened in the case, then I will break it down and follow the
variable trail... We are about to hire another person so my work load might
lighten up a bit.. yeah-right... and I can put a bit more detail into coding
like I would like. I know I fail miserably at writing in comments and helpful
coding like your talking about. As my skills improve, I am able to put in more
as I go.

Thank you for bringing up the point, sometimes we all need reminders that are
not yellow and stuck all over our monitors.

Later
Jim Limburg

--- Alastair Burr <[EMAIL PROTECTED]> wrote:
> Jim,
> 
> It's probably just the way I do it but I've always tried to give any
> computer program as easy a time as possible in the (mistaken?) belief that
> the easier I make it the better/quicker the response <g>.
> 
> With that in mind, I would normally try and set up variables and set those
> first before using edit or browse using a form with any complicated
> selection criteria. I reckon that R:Base can then find the rows I want
more
> easily and return them more quickly. I guess that it's also easier to test
> the selection if you build it up step by step and, in my case, see what
I'm
> doing wrong most of the time. Also, it's easier to see mistakes if you run
> the select(s) through trace rather than the edit/browse using syntax.
> 
> Another little trick that can be used is to output the idnums (or whatever
> is needed) to a menu so you can see what's being offered for selection.
Just
> seeing what you're getting - or not getting - can often solve a problem.
> 
> Once that's right going back to one command (if it can be written as such)
> can be tested against the separate ones for speed. If I can't see the
> difference then I'll stick with the multiple ones so that future changes
are
> easier.
> 
> Regards,
> Alastair.
> 
> 
> 
> ----- Original Message -----
> From: "Jim Limburg" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, October 07, 2002 8:38 PM
> Subject: Re: EDIT USING and IN
> 
> 
> > Thank You Larry..
> >
> > Here is what worked:
> >
> > SET VAR vm_clcknos TEXT = NULL
> > SELECT (listof(clockno)) INTO vm_clcknos INDICATOR vm_i1 +
> > FROM hrmain WHERE company = .vcmp AND status = 'active'
> > IF vm_clcknos IS NOT NULL THEN
> >  SET VAR vm_clknos = ('clockno IN (' + (CTXT(.vm_clcknos)) + ')')
> >  EDIT USING ratehist +
> >  WHERE &vm_clknos AND status = 'active' AND clockno < 9000 +
> >  ORDER BY clockno AT 1,1,650,350 CAPTION 'Update Rates'
> >  IF errvar <> 0 THEN
> >   PAUSE 1 USING 'No Matches Found. Press any key to continue.' +
> >    AT CENTER CENTER
> >  ENDIF
> > ENDIF
> >
> > I have to admit I don't understand why rbase has to parse it this
> > way, but hey... on the next challenge.
> >
> > Thank you again
> > Jim Limburg
> >
> > --- Lawrence Lustig <[EMAIL PROTECTED]> wrote:
> > > > EDIT USING formname WHERE clockno IN (.vm_clcknos)
> > >
> > > I think you need to do:
> > >
> > > WHERE ClockNo IN ( &vm_clcknos )
> > >
> > > and you probably wont be able to do this since the expression
evaluation
> > > does not like & after a ( so you would need to do it in two
steps:
> > >
> > > SET vClause = ('WHERE ClockNo IN (' + .vm_ClckNos + ')'
> > > EDIT USING FormName &vClause
> > >
> > > --
> > > Larry
> > >
> > >
> > > ================================================
> > > 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/
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Faith Hill - Exclusive Performances, Videos & More
> > http://faith.yahoo.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/


__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.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