At 06:30 2019-06-25, "Tracy Pearson" tracy@powerchurch.com wrote:
Hello Gene,
That just raises more questions about what COM object is being used to create the XLS file. Is it shipping with the latest Windows 10 computer? Is it built in to the VFP runtimes? Is this functionality suddenly going to stop working one day after the DLL is identified and removed by some anti-virus software?
Since I use pretty much vanilla VFP with very little outside stuff, I do not know. Please note that this error is due to the directory not existing. The functionality is there if the directory does exist. I was bemused that the error was different for .dbf and spreadsheet.
Before doing such copying I make sure to create the directory. I have a procedure that creates each needed subdirectory one at a time (which also deals with a bug where capitalisation is lost when creating multiple levels at a time with the VFP MD command). I have posted it before. If anyone wants a copy, just ask.
All things I don't have time to investigate.
Likewise.
Due to a different control having the same "Unknown COM status" message when attempting to have it write a file to a non-existent path, or a locked file, I have put checks in before calling the functions. Sometimes I think I should change my behavior to write to a temporary file, then move the bytes from the temporary file in to the destination. It would mean a longer save time, but I would be able to deal with anti-virus and on-demand backup tools putting a lock on the files. It's not an exercise for this month.
I create the directory explicitly first. It works for me. I am making a number of minor modifications to the system, and this nibbled.
[snipped previous]
Sincerely,
Gene Wirchenko