>>If there is no plan to have a vfpoledb provider that functions in a 64 bit environment it seems almost pointless to develop the DDEX wrapper. I would much rather see the resources expended to upgrade the data provider.
>
>There is a huge difference in the resources needed for the latter and is not part of the plans. If you plan to have a your database run on a 64-bit server, than it will be recommended that you store your data in a 64-bit database server like SQL Server 2005. Note: VFP 9.0 will run in 32-bit mode on a 64-bit machine.

Hi Ken,

Somehow I knew that was going to be the reply <s>.

In my case its dealing with data access to legacy systems, the primary data store is SQL server. I suspect there are a considerable number of ASP.NET 2.0 applications accessing VFP data using oledb. Worse yet I still see a lot of ASP.NET 2.0 development going on where the vfpoledb provider is being used.

I believe that this may be due in part to miss information being provided by a variety of sources. There should be clear signals provided to developers to not use vfpoledb for data access if they are in this situation.

I am in the early design phase of a major application upgrade that is required to access VFP legacy data. I was initially planning to use vfpoledb instead of web services. I’m glad I stumbled upon this problem now rather than later. So vfpoledb is out, should I use VFP based web services with its depreciated soap specification?

Regards,