Re: WRKDBF's "F7=Select Record" function

Hi Bill

I've never used the F7=Select either, but having just been into it to take a look I wish I'd known about it earlier. I use the SQL functionality quite a bit, well the SELECT anyway and apart from a couple of minor niggles that happen occasionally I find it really useful.

If you're looking for suggestions on the SQL and F7 functionality, how about:

* Keep the F7 functionality, but change it to use SQL to return the
record set.
* Have the number of records to scan/roll as a user option to give
more bespoke control over the Find/Select functions.
* For SQL, F7 and F4 windows retain the previously entered
criteria. If I select over multiple fields in SQL or position
over multiple keys in F4 and then want to change what I'm looking
at I have to rekey it all again.

One other suggestion, not connected with SQL/F7 is when the file name is changed at the top of the screen and it's not in the library shown WRKDBF closes and returns to the command line with a "not found" message. How about instead of dropping out straight away trying again with *LIBL and if the file is then found then loading that one.

Anyway, keep up the good work, WRKDBF is a fantastic utility.

Best regards

Jonathan


Reger, Bill wrote:

I am seriously considering removing the "F7=Select Records" functionality of WRKDBF and have been for a long time. With the vastly superior "F18=SQL" functionality it is basically obsolete in my opinion. The scan limit (which defaults to 5000 records read) often reads too few records to fill up a subfile page, which in turn confuses the user into thinking they're looking at all the selected records. Not. I personally never press F7 - ever.

But I don't want to mess up people if it is an often-used function. So what say you? Can I remove without causing too many issues?

Bill