At 09:13 AM 7/21/2006 -0700, [EMAIL PROTECTED] wrote:
...
> And, by the way, I have various config files that I use which allow my
> systems to work with the server and other networked servers with no
> problems. Of course, I do NOT use 'standard' MS config files. Maybe that's
> why mine works..... ?
What is a standard M$ config file I have no idea what your talking
about. Config.FP or web.config?
config.fp[w] [?] certainly is not an MS standard. Isn't web.config (sp?) is
the standard for .Net web pages? But other 'config' files are things like
the Windows registry, Windows system log, various .DAT files, etc.
I don't know if it was you or someone else who implied that having "config"
files for VFP on Win2003 Server was a problem. Or that VFP required a very
specific placement of all it's files. My point was I have no problems with
my VFP systems on Win server 2003 but I design my own resource (config)
files that I can rely upon.
Bottom line: the less you rely on Windows for various services, the better
protected you are from patches and even OS updates.
-Charlie
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** 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.
