Hi Steve;

   Just wondering if it's somekind of "contention" issue? If so, maybe a Yield() command & then a "retry" (or two) might get around this issue? Food for thought. HTH

Regards ... Chris

We have made a change to sleep(30) if the filemove fails with -2. this seems to solve the issue for now. The file is still growing and that is why it fails to move. I would have thought that this was a source file error, -1, and not a target file error of -2

We use a pdf distiller to print the reports as pdfs. This is the same version we used with PB10. Does the datawindow print in PB2019 send more data to the print queue than PB10 did? The print queue is reporting that there is 22MB of data when printing and the file size is 800K. we never looked at this before so I don't know the answer myself.

We have tried a yield() and a sleep(). we have also tried the filemove again when it fails with a -2.

Hi, Steve - 

I don't know if any of these options are workable for your particular situation:

1. Try using the FileCopy/FileDelete PowerScript functions instead of FileMove, maybe just with very large files.

2. Use Windows' Robocopy utility (command prompt) via ShellExecuteW or ShellExecuteExW WinAPI commands (refer to the RunAndWait free code example program on Roland Smith's TopWizProgramming web site). Robocopy is pretty robust and has a /MOVE option...type ROBOCOPY /? from a command prompt to see all available options. It also has retry options and logging options. You could also use a .BAT file to encapsulate the Robocopy command(s).

HTH, John

reran the PB10 version of the app and the datawindow print method only pushes 9MB of data to the pdf distiller.

Why is the PB2019 datawindow.print() method pushing so much data? Can this be changed? 

Steve -

If the FileMove command failed with a -2, try using FileCopy followed by deleting the source copy of the file if the COPY worked.

Also, check the RIGHTS associated with the user trying to do the Move and/or Copy.


Good Luck,

Olan