Hello Mark,

Glad to hear that you are advancing in your VFP expertise.

i was just wondering since you also have done check printing, did you ever come across this requirement of updating lprint field as i mentioned in my previous messages here. i mean how do you print your checks?

All at once. Every record that is to be included on the check(s) is marked with a -1 in the check number field. The app asks the user to confirm the next check number (like that big fancy app) just in case one was written by hand since the last printing. The check numbers are assigned just prior to running the report, and all records to be printed are marked with a flag in a one-character field; the report is filtered to include only those records.

It was just a few weeks ago that I got a panic call from the client - "I pressed the cancel button before the checks were printed!! Help!!!". It had been two years since I looked at the code, but I soon remembered that I could just REPLACE ALL chknum WITH -1 FOR chknum > 1233 (1234 being the next check number in the pile). One eternally grateful client. The dates of the records confirmed that the correct subset of records was unmarked.

So that may not be the most exotic or brilliant method, but it worked for me and that client.

You're welcome,