>>>>by "Design For XP test application" do you mean the application called "AppVerifier" that comes in a windows testing SDK pack?
>>>
>>>Hi Chris,
>>>yes I mean the same.
>>>If our application past and VFX RAD framework past it 2 weeks ago there no reason your application to crash
>>
>>How do you tell VFP to find the CONFIG.FPW and FOXUSER.DBF a different way?
>>
>>A small section of the log when running a simple VFP app (single PRG compiled as EXE) is as follows:
>>
>>

>>| FilePaths 1 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\config.fpw'.
>>| FilePaths 2 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\config.fpw'.
>>| FilePaths 3 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\config.fpw'.
>>| FilePaths 1 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\config.fpw'.
>>| FilePaths 2 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\config.fpw'.
>>| FilePaths 1 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\System32\Wbem\config.fpw'.
>>| FilePaths 2 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\System32\Wbem\config.fpw'.
>>| FilePaths 3 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\System32\Wbem\config.fpw'.
>>| FilePaths 1 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\FOXUSER.DBF'.
>>| FilePaths 2 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\FOXUSER.DBF'.
>>| FilePaths 3 | 2 vfp8r.dll 20960'Hardcoded path found in path 'C:\WINDOWS\system32\FOXUSER.DBF'.
>>

>>
>>So VFP is not retrieving system paths using functions correctly in the API it seems? Is this a configuration option because the VFP8 IDE doesn't throw these errors (although I do realise that the VFP IDE isn't a VFP application...)
>>
>>Chris
>
>Chris -
>I find it strange that your config.fpw and foxuser.dbf files are in the system32\.. directories. Did you design it that way ?
>IMO - they should not be there - but should be in the root of the application directory.
>OTOH - if you have your app in the system32 directory - *THAT* , in itself, again IMO - is a bad thing.

Interesting point, Bill.
I've NEVER seen/used the "appverifier" utility, but a few things come to mind after reading this thread so far:
1) *IF* the appverifier allows running multiple time, checking specific factors each time, then possibly the way to get through it successfully is to run the same test several times, specifying a different 'check factor' each time.
2) Possibly the appverifier adds extra tests when the application is run from system32\.
3) related to #1... possibly there are 'bugs' in the appverifier that option 1 circumvents.
It appears that there may also be a lack of documentation for the utility OR that it is there but in a not so obvious place.

Given that other VFP apps have succeeded, I'll bet that ChrisO WILL succeed sooner or later.

cheers

>
>regards [Bill]