The config file is built-in to the app and is the same since 1997. On a lan
with 6 workstations running vfp6 or 9, the breakdown of operating systems
is:
Win7 home (ignores setting, uses appdata/local/temp instead of C:\temp)
XP pro sp3 (ignores setting, uses appdata/local/temp instead of C:\temp)
XP pro sp2 (uses C:\temp)
XP home sp2 (uses C:\temp)
Vista home basic (uses C:\temp)
Some offices are also reporting that the default folder (on the server) is
getting the .tmp data. I have seen this when I download their backup data
for storage.
I don't mind if the data goes to appdata/local/temp, as apparently windows
(some versions) is taking care of disposing of it. ... but when it goes into
the default folder it can lead to real problems later on.
If anyone has a better way to store the temp data, I'd love to know.
Post by Gianni TurriAre you sure that they are still using your config.fpw file?
Gianni
On Thu, 6 May 2010 07:57:02 -0400, "Foxteeth Doc"
Post by Foxteeth DocNope... they all have the C:\temp folder... it's part of our installation.
Post by Bernhard SanderHi Wade,
Post by WadeMy config file has tmpfiles = C:\temp (a folder I install)
also I have progwork, sortwork, editwork the same.
For years, all the .tmp files went into C:\temp and were deleted in the
program when appropriate.
Now, some offices have all these files going into the default folder on
the server, and some have them going into appdata/local/temp.
Why doesn't my config file control all these? It used to.
Maybe because C:\temp does not exist on the computers of these offices.
A default installation of newer windows have a different location of the
default temp folder
Regards
Bernhard Sander