Tell me about it, Jim, too much to do & too little time to do it for hardly
even a "thank you" most of the time.

But really! You can see your monitor!?

I forgot to say that you can also leave the test commands in your program
and just comment them out then when it goes wrong - yes, when! - you've got
half the work done in finding out what's changed. Sometimes I move them to
the end of the program out of the way but it saves thinking how to do it all
again.

Good luck,
Regards,
Alastair.



----- Original Message -----
From: "Jim Limburg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 12:52 PM
Subject: Re: EDIT USING and IN


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

Reply via email to