>The same app on the same server\share is being accessed using different invocations from 2 different environments. But, you have only 1 config xml file which is being used by both. That doesn't sound ideal:
>
>- As you suggest, one way to address this would be to use the EXE's starting folder rather than relying in the value in the config xml file
>- Or you could use separate/custom config xml files for each environment
>
>I've been speculating that VFP may not (fully) support FQDN-style UNC addresses. Can you do some testing to check this:
>
>- For users(s) using FQDN, try ADIR( ) and FILE( ) with FQDN-style UNC to look for a file that you know exists and is not built-in to your EXE
>
>Either test might bomb out with a syntax or some other error (i.e. not supported). OTOH if the tests work and return the expected result then maybe VFP9 does support FQDN-style UNC addresses.

As you suggested, I have tested the use of FILE() with the FQDN-style UNC and it works. No error, no problems. So, it appears that the FQDN-style UNC is supported by VFP 9.
Therefore, maybe, the initial problem I experienced was due to some network glitch or something that is not caused by the VFP 9 application.

Ideally, I would like to add a test "bug" in the program and to see how the application - that connects to the server via FQDN-style UNC - will log the error. Whether the the initial error of the error manager library will be found or not. I suspect that the initial error was a glitch but it would be nice to dig in deeper.