Some Sort of Control From The Browse Screen

[Rkreiss@verizon.net]]

Scott,

Per my off list response, you could run a browse selection option at @entsel nad use dokey for either type of browse.

Thst probably is the closest to having @key functionality in a browse.

This would also allow you to change the browsw format on the fly.  

I have one application which allowse for a item search on orders wherethere can be 250 detail lines.  The same app allows for dispalying order details by item #m description  or by how the lines were entered.

Ads an aside to this whole issue.  Be aware that a browse cashes the record #'s of the records being displayed.  This allows for faster redisplay of the browse records on reexecution.

I ran into an issue withthe above client where f order clerks were entering orders and the billinh clerk would delete those order detail lines which were not shipping.  Every so often, a detail would be deleted and the billing clerk would complain that on reexecuion of the browse, after the deletion, are detail line from another order would appear.

With the speed of today's systems, thee deleted record would be picked up by one of the order clerks entering a new order and it would be returned to the billing clerks browse based on the record #.  I had to add a drop to the browse to insure thst only the order being billed detils appeared.

This took Ken's able assistance as Tech support could not duplicate the working envirnment where this was happening.  

I keep wondering if there are any other areas where the speed of today's systems could have unexpected adverse effects on porgrams.  Yes, I do use the sleep command to pause processing after a close to give everything a chsnce to porcess.  

Of course, other programming methods we wouldn't have used years ago as too slow, we don't consideer today as a problem as the systems are much faster