That reminds me of a bug I encountered once. We had an app that kept crashing and couldn't figure it out.
Finally, I went to the location and did some digging around. It turns out that our code used a file in the Temp folder for some reason I can't remember. Our code checked to verify that the temp folder existed. What it didn't do was to see if it was read-only or not (this is a "Temp" folder....) Anyway, it turns out that the IT folk at the time had decided to lock down the Temp folder on all machines - but only by making it read only...... The worst part is that, while we couldn't write to the file, we could open it, etc. And when we tried to write to it, it acted like it did, even though it didn't.... But then crashed later when we used it again and the necessary values weren't there... This was back in the very late 90s, so don't bother asking me for more details.... Fletcher Fletcher Johnson fletchersjohn...@yahoo.com LinkedIn.com/in/FletcherJohnson twitter.com/fletcherJ strava.com/athletes/fletcherjohnson 408-946-0960 - work 408-781-2345 - cell -----Original Message----- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Tracy Pearson Sent: Tuesday, June 25, 2019 6:30 AM To: profox@leafe.com Subject: RE: Odd Error Message 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? All things I don't have time to investigate. 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. All things in their time, Tracy -----Original Message----- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Gene Wirchenko Sent: Monday, June 24, 2019 6:15 PM To: profoxt...@leafe.com Subject: Odd Error Message Hello: I got an interesting error message today. It was another example of an error message indicating that an error had occurred with the message not terribly useful for determining the actual error. Try the following use sometable copy to nothere\nothere\sometable copy to nothere\nothere\somecopy type xl5 where sometable is some table and nothere\nothere is a non-existent subdirectory chain. The error message for the first copy command is "Invalid path or filename." This is sensible. The error message for the second copy command is "OLE error code 0x80030003: Unknown COM status code." Huh? Copying to a directory that does not exist results in an error. You even get a choice of error messages. Sincerely, Gene Wirchenko [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/032101d52c41$36a0ec70$a3e2c550$@yahoo.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
