Browser lookup

[Kenneth Brody]

On 10/20/2010 4:08 AM, Rkreiss at verizon.net] wrote:
> Since I am on vacationm this is the first time I have a chance to reply.
>
> Based on how this thread as gone with regard to updating real fields from auto processing, my solution of using a browse lookup from a library file would eliminate this problem.
>
> The only thing a user could do would be to update field 5 by pressing "u" using @bk=u.
>
> One might get the record # of this record, branch to a protected lookup by record # and then toggle the value either to "y" or blank.  Then return to the browse.
>
> Access to the primary file can be occur by using exit values handled by the menu script.
>
> Exit 99 Exit to menu
>
> Exit 55 run clerk on primary file.
>
> Simple processing with the ability to add more options for updating a record from a browse.
>
> I have built up a fairly extensive library of these types of browses for different uses by vsrious clients. I can point one of these programs at any file and easily modify if for a new function or client.

I still don't see why you want to go through all that hassle when a simple 
browse lookup would suffice in the first place.  No library files, no 
decoding exit values, no scripts, just a simple browse lookup.

-- 
Kenneth Brody