Another customer problem: a product doesn't work with VFPhttp://blogs.msdn.com/calvin_hsia/archive/2004/12/03/274680.aspxA customer reported that a product they have doesn’t work with Visual Foxpro . Time to put on the detective hat! In the command window, type o= CREATEOBJECT (“ABCProduct.Application”) After hitting the Enter key, the FoxPro process crashes. I tried fromen-USCommunityServer 2.1 SP1 (Build: 61025.2)re: Another customer problem: a product doesn't work with VFPhttp://blogs.msdn.com/calvin_hsia/archive/2004/12/03/274680.aspx#274800Sat, 04 Dec 2004 01:29:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:274800Raymond ChenThe value 0xFFFFxxxx is a wndproc thunk. <br> <br><a target="_new" href="http://weblogs.asp.net/oldnewthing/archive/2003/12/01/55900.aspx">http://weblogs.asp.net/oldnewthing/archive/2003/12/01/55900.aspx</a> <br> <br>The bug is that they are calling the function pointer directly instead of using CallWindowProc. <br> <br>It looks to me that they're an ANSI application using comctl32/v6. This is not a supported configuration. Comctl32/v6 requires that the program be UNICODE.re: Another customer problem: a product doesn't work with VFPhttp://blogs.msdn.com/calvin_hsia/archive/2004/12/03/274680.aspx#275785Mon, 06 Dec 2004 18:22:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:275785CalvinH [MS]Raymond: Thanks for the details of the problem. It gives more confidence that GetClassInfo was working correctly, and guidance to the customer.Third Party application does work as a COM+ applicationhttp://blogs.msdn.com/calvin_hsia/archive/2004/12/03/274680.aspx#410941Fri, 22 Apr 2005 23:41:59 GMT91d46819-8472-40ad-a661-2c78acb4018c:410941Calvin Hsia's WebLogA few months ago, I reported a problem that a customer was having with a particular 3rd party product...