One big question, "What gains do you expect to make by going to 64 bit?" Many times there is no business case. 64 bit applications are starting to make their way onto the server. For example, the next version of Exchange is 64 bit only. But on the desktop, 32 bit will work just fine for the majority of business apps for some time.

Now, if the user insists, I recommend doing development work in something like .Net, where moving from 32 to 64 bit is fairly easy, so long as you've kept with standard data types.



>Firstly, thank you all for your response. I worded the question incorrectly and I apologize. One thing has been made perfectly clear in the "roadmap," FoxPro is not going to be converted into a 64bit development tool. It's really the one non-vague statement.
>
>My question should have been, when new prospects or customers are considering software for their business, what will you say in response to their desire for "modern" 64 bit applications? You can't down-play 64 bit, and if you want the business, how will you handle it?
>
>We believe one of software criteria (as recommended by consultants) will be for businesses to invest in a "long term" solution which means getting "newer" technology, which means 64 bit will recommended.
>
>As a veteran assembly programmer, who has done extensive protected mode programming from 16 bit to 32 bit (in the early 90s), and putting aside the database 32 bit issue (because we could use an SQL backend), converting VFP to 64 bit may be a challenge, but far less a challenge than we're being asked to undertake in switching to a new development platform where all prior code and resources are scrapped and one has to start from scratch (not to mentioned FoxPro is one program where there are countless programs written in FoxPro).
>
>Again, thank you for your input.