Kudos to Mr. Ormerod....

Now this is indeed interesting...and an issue that is worth making a fuss about.

FWIW gang, this is the type of stuff that is worth getting PO'd about. This is the type of thing you need to hit Ken over the head with. This is something that is fairly objective. You know...an app is either certified or not. And...if Fox makes API calls that defeat certification, then it follows that you cannot create an XP-Certified-Logo app in Fox. And what does that mean???? It means that for those who wish to keep thier partner status in fact, they are FORCED to leave VFP in favor .NET/SQL Server...

This has nothing to do with emotion or irrational feelings. What Mr. Ormerrod has brought to light here - assuming it is all accurate - and it sounds like it is - a bona-fide issue with continuing to do VFP development - none of which is technical in nature.

It seems to me that if at a low level - VFP makes unsupported API calls - there is no real work around to the issue.

And FWIW, I absolutely believe it is 100% intentional. My guess is that a VB 6 app could not be verified. Although if it could, that alone should send a BIG message - one that is loud and clear. It would certainly defeat the arguments that VB is "dead".

You have a legit issue here - and it is one that I would be concerned with. Start hammering on Ken to get an answer. It seems to me that if MS is still developing a product - and is still selling the product - you should be able to build XP-verified apps with it.

That said...keep in mind that when 95 came out, for a while, 95-certified apps could not be built in VFP becuause VFP did not have the ability to create context-sensitive menus (at least to the degree necessary for certification).

Good luck...



>We are just wondering if anybody has managed to get a VFP app certified for Windows Logo (or similar programs), apparently we have been told that to maintain our Microsoft Certified Partner status next year we will need to get 50 "partner points", and the easiest way to get these is to have our app pass 2 certifications - one is the SQL Server/ODBC/OLEDB one which to pass our application just has to make use of ODBC or OLEDB to connect to SQL Server 2000, the other is a "Verified for Windows XP/2003" certification, and as part of this our app has to pass the tests in AppVerifier from Microsoft.
>
>Issues with this are:
>- When AppVerifier is running our app crashes with C000005 errors quite often.
>- VFP8 (and the .Net framework) read registry keys that are denoted by AppVerifier as shouldn't be read by an application and as such our app fails.
>- VFP8 calls unsupported API functions (such _LLSEEK etc) which again fails the AppVerifier tests.
>
>Is this something we should be able to work around with a bit of time or is it an issue in VFP 8 that we won't be able to resolve? So far I have only spent about 1/2 hour playing about with this AppVerifier program so hopefully there are options in there we can fiddle with to make it work.
>
>Chris.