Just to complete a little more what I wrote: For Development I use a directory structure like this
\root-app-dir => Directory from where I run the code and the EXE, and when MAIN.PRG is \config => contains the config.fpw included on the EXE/APP \classes \progs => All PRGs EXCEPT main one, that is on root app dir \DATA => DBFs, CDXs, etc (AV excluded DIR) On Production, the directory structure is a subset: \root-app-dir => EXE \DATA => DBFs, CDXs, etc (AV excluded DIR) 2018-04-09 19:19 GMT+02:00 Fernando D. Bozzo <fdbo...@gmail.com>: > Hi Paul, > > 1. Occurred to me, and I think that *could* have something to do with > Windows Folder Virtualization > > 2. When Windows can't write to your CFG dirs, then automatically select > the TEMP > > In my experience with this "strange" errors, I've fixed them creating a > subdirectory by user behind a public one --well ahead of Windows own dirs-- > with all the permissions necessary (ie: "C:\APPNAME\DATA\USERX") > > I have 2 solutions for this up to now, and in both of them Windows can't > interfere in any way, and you just want to configure de AV software to > ignore it: > > > 1) When the PC is not shared between users: > > This is the most simple case, and all you need is to create a DATA > directory (ie: "C:\APPNAME\DATA") and a CONFIG.FPW with this directory for > all config items > > > 2) When the PC (Server) is shared among users: > > This is a little tricky, but with you can asure that user TMP files are > well separated, and requires a "launcher" file (can be a VFP or a VBS > script one) that before starts the VFP APP/EXE, creates a "personal" CFG > file for each user (ie: "C:\APPNAME\DATA\USERX\config.fpw") with all the > paths ponting to this dir, the launches the VFP APP/EXE with the *-C* > C:\APPNAME\DATA\USERX\config.fpw option > > You even can use an internal CONFIG.FPW with starting exactly with this > lines to allow using the external CFG: > > * internal config.fpw > ALLOWEXTERNAL=ON > RESOURCE=OFF > > > Hope it helps. > > > 2018-04-09 18:46 GMT+02:00 Paul H. Tarver <p...@tpcqpc.com>: > >> I think this is a two part question for VFP9: >> >> >> >> 1) Has anyone had any experience with getting a program error at >> runtime like this: File c:\users\paul\appdata\local\te >> mp\xxxxxxxxxxxxxxx.tmp >> is read-only? I do not get a similar error when running in development >> mode >> and I have explicitly set SORTWORK, PROGWORK, EDITWORK and TMPFILES in the >> CONFIG.FPW file. >> >> 2) Why does VFP continue to create cursor temp files in the >> aforementioned path at all when I've manual set the path for temporary >> files >> in the CONFIG.FPW file? >> >> >> >> I'm sure it is something I'm doing wrong, so feel free to provide >> constructive OR destructive criticism. J >> >> >> >> Thanks! >> >> >> >> Paul >> >> >> >> >> >> --- StripMime Report -- processed MIME parts --- >> multipart/alternative >> text/plain (text body -- kept) >> text/html >> --- >> [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: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAGQ_Ju=1N5xeCfAnu0i1zkhMnMHJota2k3i=o5m9np6htk9...@mail.gmail.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.