>>>>>>>>I'm sorry, but I don't understand your response.
>>>>>>>>WILL the 32-bits apps work in Windows 7 (64-bit)?
>>>>>>>
>>>>>>>64/32 bit is not the problem. Security being tightened from XP in Vista/Win7 is - regardless of bit size.
>>>>>>>Another problem you will/might have with Vista/Win7 vs. XP is SMB2 and/or OPlocking for accessing dbf in multiuser mode on a server.
>>>>>>
>>>>>>Do you have any solution for SMB2 besides going back to SMB(1)?
>>>>>>Anyone has experience with SMB3 of Server 2012?
>>>>>
>>>>>I am guessing the message of MS is to stop using ISAM file based multiuser db and start using db servers -
>>>>>the tendency to WLAN cannot be blamed on MS and makes file based db access also more problematic.
>>>>>
>>>>>If it does not work out of the box, don't fight uphill battles. The free versions of most commercial db servers
>>>>>are usually capable enough, Postgres is free and can sling heavy loads, others are in between in price
>>>>>and offer sometimes tighter integration to newer systems - vfp with fileserver-dbf in writeheavy situations becomes a liability.
>>>>
>>>>Sounds like a bunch of trolling FUD to me. MS is NOT conspiring against Foxpro and/or file based data - give me a break. It's not even on their radar!!
>>>>
>>>>Most things VFP will probably work fine with Windows for the rest of our lives.... (maybe the Fox GUI interface will have issues but that's a minor thing. VFP data and code WILL continue to work fine despite the FUDSuckers here)
>>>
>>>You are aware of the SMB2 issue with VFP, Access and other ISAM file-based databases? It will likely never be fixed. See the thread http://www.levelextreme.com/DataEntryThreadView.aspx?ID=1430067
>>>
>>>Also, Michel Fournier, the owner/operator of the UT, found that the latest available VFP OLEDB provider is not reliable under load. After much back-and-forth with MS, that's another issue that will not be fixed. Arguably, this shouldn't be too much of a problem because OLEDB is being deprecated by MS. But, the situation with ODBC is even worse, the latest driver only supports VFP6, and none of the data/database changes made since then are supported.
>>>
>>>Interop with 64-bit apps is challenging. Might not be a big problem now but it'll only get worse.
>>>
>>>MS is not so much actively trying to kill file-based databases, instead it's neglect and/or lack of testing. SMB3 is coming out in Windows 8/Server 2012, both are still in RC. I don't know if anyone has set up an environment with these OSs for testing but chances are the community is going to have to do it, because MS probably won't.
>>
>>MSKB articles describing the SMB2 issue with Access and FoxPro:
>>
>>http://support.microsoft.com/kb/935366
>>http://support.microsoft.com/?kbid=935370
>>
>>ISTR Brandon Harker spent a lot of time on an elevated tech support incident with MS. I believe the hotfix referenced in KB935366 was tested and found to not fix the issue (at least with VFP, I don't know about Access).
>
>But please do not feed into all of this paranoia that there will be a problem with VFP (as refuted above by your initial references, no less). Microsoft is not trying to kill file-based dbfs and it is REALLY ridiculous to think so! Also, it is highly unlikely this will be a problem by accident since SO MANY would be adversely affected (not just foxpro!) - which MICROSOFT DOES CARE ABOUT.

The first reference (KB935366) talks about a hotfix, but that hotfix was tested and it does NOT fix the problem with VFP running on SMB2. This is a real problem that people are having to deal with, whether you want to believe it or not.