I'm having a problem with a kludge which works when the PRG is called from the command window, the EXE is called from the command window, but fails when the EXE is called from a DOS prompt (or the Task Scheduler - which is my eventual objective).

Here's some background......

In the main application, the user opens a policy and then navigates to a screen from which the policy can be issued. This sets up a print job which is passed to a different program to do the actual printing.

We are looking at changing the print formats from hard copy to PDF's. I can do all that on a policy by policy basis. The problem is that I need to regenerate these PDF's for about 30,000 previously issued policies.

My kludge was to stop the program at the point where the user would click an < OK > button. I then did a SAVE TO .mem file and a CREATE VIEW to a .vue file. I now have a routine which does a RESTORE and SET VIEW TO. I then to the main (POLICY), cycle through the records which still need to be processed, move the record pointers in those tables which require it, and call the issuance program. Hard though it may be to believe, this actually works.

I've compiled all this into an EXE which works.

Here's the problem....................

The data on which this works is FPW2.6 tables which are zipped up and copied nightly onto my workstation. When I do my SET VIEW TO operation in the command window, all the files open properly. When the EXE is run from the command window all the files open properly.

However, when the Task Scheduler (or DOS window) calls the EXE, I get the "Select Code Page" window.

Is there some setting I can pass in through a CONFIG.FPW file or by a SET command in the program which can avoid this?

If I were to open the real source files in VFP and attach a code page to them, would that be retained when they are zipped up and the put on my workstation?

Any other suggestions would be greatly appreciated.

Thanks to all..........Rich