>A bit of recap for lurkers:

And one observation / experience;

Ever since SMB2 issue popped up into public attentio,n I was requesting network guys to disable it for any new server/installation.

However in one instance this was NOT done so SMB2 remained in operation and remained so for very long time.
I realised that SMB2 was in operation for over a year (which caused fumes/flames coming out of mu nose)
So finally we disabled SMB2 and everything went on as usual.

What I am trying to point out is observation/realization that; There was NO corruption not so ever for over a year!
And we are talking about app that actually uses shared VFP tables kept on server.

Data access scenario I use is to have ALL tables buffered at ALL TIMES (optimistic 5) and every time anything is written into
any VFP database/table, it is always done inside beg tran/end tran transaction wrapper.
(Built in functionality universally applied)
Server in case was WS 2008 SP1,

What I am wandering now (and question to SMB2 issue experts) is
Was I just lucky SOB ? Or, does applying buffering/transactions (or version of server) make any difference in this respect ?

I hereby DO NOT advise against or for using SMB2, I am just stating observation / experience.