Hi Jim,

Yeah I have been playing about with your option 1, the AppVerifier works by you tell it the EXE file of your application and then there is a list of "tests" that you can turn on and off individually, by doing this I have had more luck running it with just 1 test turned on at a time.

As I explained to Bill our app isn't running from the system32 directory, it just seems VFP is looking there for some reason.

Also on the documentation for this tool, there is plenty - but it is all just general and relates to what the tests are checking for. The thing is this tool has no options apart from where you input the path to your exe, tick the tests to turn on, then click run, then view log. So apart from carefully picking the test combinations to be compatible with VFP there isn't much I can think of to try.

The only other possibility is that (seeing as others have their VFP apps certified) the testing centers may know about issues in the VFP/VB/.Net runtimes and not fail applications based on errors in the actual runtimes of the systems?

But yes I think you are right that I will succeed eventually, just have to find the right combination...

Chris.

>
>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]