Once had a network admin move everyone's "Documents" folder to a shared network path. Then didn't allow anyone to see the contents of the folder above it.
\Server\Share{UserName} was how it was done. The user was able to put things in C:\Users{UserName}\Documents and everything worked. So user couldn't write or see anything in the Share folder. But was allowed full access in their folder.
Getting the SpecialFolder from windows and doing a "SET DEFAULT TO (cDocumentsFolder)" would throw "Invalid path or file name (Error 202)".
Odd errors...
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Fletcher Johnson Sent: Thursday, June 27, 2019 4:37 PM To: profoxtech@leafe.com Subject: RE: Odd Error Message
We did have a test to see if the temp folder existed. If it didn't we tried to create it. But it did exist. Given the purpose of the temp folder is to hold temporary data, we didn't bother with code to actually try to create a file, write to it, and then verify that it was written to. I mean, who would ever make a temporary folder read-only????
Anyway, once we figured it out, it was easy to fix.
I don't know why VFP (I can't remember which version we were using) didn't complain about the problem - it's been too long. But I do know that our error handler did not get called and the code happily continued executing even though the write was not actually performed. We used both On Error as well as Try Catch when it was finally added.
Fletcher