RE: Bizarre Desktop write problem driving me mad

2021-03-31 Thread Tracy Pearson
Is the EXE somehow running in a sandbox, or compatibility mode? Tracy -Original Message- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Vince Teachout Sent: Tuesday, March 30, 2021 12:43 PM To: profoxt...@leafe.com Subject: Re: Bizarre Desktop write problem driving

Re: Bizarre Desktop write problem driving me mad

2021-03-31 Thread Vince Teachout
Thanks, Alan.  I checked it out, but that isn't the problem. :-( On 03/31/21 7:03 AM, Alan Bourke wrote: Maybe try snagging Doug Hennig's specialfolders.prg from here: https://doughennig.blogspot.com/2007/01/finding-paths-for-special-folders.html Then see what specialfolders("desktop") return

Re: Bizarre Desktop write problem driving me mad

2021-03-31 Thread Alan Bourke
Maybe try snagging Doug Hennig's specialfolders.prg from here: https://doughennig.blogspot.com/2007/01/finding-paths-for-special-folders.html Then see what specialfolders("desktop") returns in case Windows is up to some sort of shenanigans. -- Alan Bourke alanpbourke (at) fastmail (dot) fm

Re: Bizarre Desktop write problem driving me mad

2021-03-30 Thread Vince Teachout
Nope, none of the below apply.  Shorcut is the default, and the behavior is the same if I navigate the path from c to users to vinny to desktop. vinny is well under 8.3.  My full path for the TO is a variable (same as yours, actually) with the value: "C:\USERS\VINNY\DESKTOP\MYTEST.PDF " On

Re: Bizarre Desktop write problem driving me mad

2021-03-30 Thread Ted Roche
On Tue, Mar 30, 2021 at 10:08 AM Vince Teachout wrote: > Granted, it's a short drive, but > I know the feeling. I can walk from here ;) > This is making me nuts. I've paraphrased and simplified the problem to > the gist of it: > > My program does COPY FILE (cInputFile) to (cOutputFile).