hi again Chris & Roland, super thanks for all that info, hope I didn't waste too much of anyone's time. I got it installed and working with ease, the Saveas to PDF works fine now, step 1 handled.
Step 2 is dealing with how this current auto-print-pdf home-grown app of ours is refusing to send PDF's where we want. Current code is programmatically setting up a ref to a 3rd party printer/driver ("CUSTPDF", no longer available I think), in the below fashion...
RegistrySet("HKEY_CURRENT_USER\Software\CUSTPDF", 'OutputFile', RegString!, a_filename)
ids_DataStore.Modify ('DataWindow.Printer="CUSTPDF"')
("HKEY_CURRENT_USER\Software\CUSTPDF", 'Orient', RegString!, ls_orient)
("HKEY_CURRENT_USER\Software\CUSTPDF", 'BypassSaveAs', RegString!, '1')
...but the box also has the "Sybase Datawindow PS" printer set up, and set as default. With this arrangement the app is printing PDF's fine, to the output folder we specify, on our old box.
With our new box and what I'm trying to set up, even with the Ghostscript/Sybase Datawindow PS printer set up now, and running the above code, the app throws up a prompt window demanding the file type and path. It will only directly print PDF's (still) if I point it to the "Microsoft Print to PDF (redirected)" printer, and always sends them to the local machine \Documents folder, very frustrating. I can't help but think this is something to do with the way the above registry refs are pointing the thing to the printer, but tests remain to do. Any input/ideas on solving this last hurdle would be much appreciated.