show only browse

[Bruce Easton]

  Well Richard, that oddly looks like the solution in my posts on 9/15 
and 9/16 - the only difference being that the good-ole display command 
works just as well.  Had you tried that solution without first getting 
involved in key-capturing, @entsel, automatic processing, switch-to, 
etc. etc., you would have been finished long ago.

I recommend that you not stab at a solution with bits and pieces of 
whatever people say here in chronological order, because one problem 
here is that people tend to read one post, then reply to it with their 
expertise, sometimes even going off into never-never land, without first 
reading all posts to date on the subject before replying.  This 
frequently causes good solutions to get lost and surpassed by posts with 
questions that have already been answered.

Bruce

Bruce Easton
STN, Inc.




On 9/17/10 12:52 PM, Richard Kreiss wrote:
>
>> -----Original Message-----
>> From: filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com
>> [mailto:filepro-list-bounces+rkreiss=verizon.net at lists.celestial.com] On
>> Behalf Of Fairlight
>> Sent: Thursday, September 16, 2010 6:06 PM
>> To: filepro-list at lists.celestial.com
>> Subject: Re: show only browse
>>
>> When asked his whereabouts on Thu, Sep 16, 2010 at 05:46:32PM -0400,
>> Richard Kreiss took the fifth, drank it, and then slurred:
>>> At this point in time, the programming works and I really don't have
>>> the time to see what is clearing the browse without a clearb.
>> Translation:
>>
>> ``I have no idea why my code "works", but it seems to present the desired
>> behaviour right now against a limited test data set, so I'll just assume
> it's fine
>> because I'm in a hurry and can't be arsed to make the effort to learn
> -why- it
>> does what it does.  But in the future when that lack of knowledge bites me
> in
>> the rear, I'll pay for today's impatience in time and money.''
>>
>> That's not a personal attack.  That's a general interpretation.  I've
> heard this
>> swan song before--usually about 3-6 months before someone blows $3-10k
>> tracking down a problem that's not fresh in anyone's mind by that point
> and
>> requires half a week or more of analysis, but which could have been fixed
>> with about 2hrs more persistence by the programmer at development time.
>>
>> Usually, when you don't know -why- something does what it does, or
>> doesn't do what it should, there's an issue that will come back to bite
> you.
>> No code should ever go into production without -knowing- exactly why it
>> works the way it does, IMNSHO.
> Mark,
>
> The final code being used is as Dennis and Ken suggested and works.
>
> What I was saying was that I don't know why the browse closed when<enter>
> was pressed in my original version.  I don't want to spend the time now to
> figure this out why the browse closed with no CLEARB.
>
> Final code:
>
> Browse
> SHOW "@"
> Switchto sn  (browse closes)
> END
>
> Richard
>
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>