>>>>>>>>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.
>>>>
[G.W.]
>>>>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!!

Hmmm, lets see: I [also] mention technical grounds not under MS control (WLAN) which make file based DB unstable and
the documented errors in SMB2 multiuser access not being repaired in Win7 after first surfacing in Vista.
The second might be overinterpreted in my "message of MS is to stop using ISAM file",
but "MS is [NOT] conspiring against Foxpro and/or file based data" is nowhere mentioned in my text -
seems to me you build up a straw man for your FUD allegation... I am not into F and U, and for the third

[G.W.]
>>>>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)

Sure, all those reported VFP or ISAM data problems will evaporate when your code runs or you sit at the machine,
even if it is a Win7/Vista client connected to a Win7/Vista server doing multiuser access.
Now who is in Denial mode ? Hint: not me

>>>
>>>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

....snipped

>>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).

As there currently IS a problem, I interpret the "will" to be future and to concern Win8
and that you believe the problem will be fixed there.
Have you tested this with the code Brandon showed on some beta install of Win8 ?
If so, which beta / what code failing under WIn7 but working under Win8 ?

>Microsoft is not trying to kill file-based dbfs and it is REALLY ridiculous to think so!

Wow, high level technique: straw man refusal, as this was brought up by yours truly alone...

>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.

So, as the described and even MS-acknowleded problem in your opinion is "unlikely by accident" - how came it into being and stayed so?
Divine intervention ? Aliens ? Bacteria ? Skynet ? Anonymus Hackers ? NSA backdoor ?

Do you have anything [new] to say about technologies involved or
at least tested on the mentioned error showing conditions to backup your posts/opinon ?