Ok I have a question about the ODBC driver thing you said.
If I have a VFP application that uses remote views to access VFP tables and I'm using ODBC to do this, does this mean it's not going to fly on 64bit windows? And same with remote views using ODBC to hit SQL Server tables? I've been writing my apps this way for a while so when I have a client that wants to switch from VFP tables to SQL tables, all I gotta do is change a connection string in my DBC...and poooof! I'm done.... I'm just real carefull on how I design my VFP tables so zero conversions are required to move them to SQL tables. For a long time I thought this was a pretty slick idea....

>The question was, "What do you tell your customers". If I tell them it "will" and then for some reason it doesn't, who will the customer blame?
>
>Additionally, there may be issues that cause a VFP app to not run. 32 bit ODBC drivers won't work on 64bit Windows. What if the application accesses some obscure database that the customer has and 64 bit ODBC drivers aren't available? What about ActiveX controls? Do I know for sure they'll work?
>
>Bottom line, there are lots of issues that can still cause a VFP app to not work on 64 bits. Hence, "should".
>
>>"Should". You wouldn't say "will"?
>>
>>If not, what do you know that we (well, *I*) dont'?