>I'm referring to "Anything anywhere else is restricted by UAC permissions... C: drive, E: drive and network drives it doesn't matter. " and the rest of the paragraph. Suppose you have a file sharing app, be it in dbfs, or something in Access or perhaps Paradox or any other such app out there - is there any guarantee that the shared tables will be accessible, that the record locks will work, that no virtualization would create phantom copies without users' knowledge? ...Unless these permissions are part of the setup, or the app somehow refuses to work if they aren't set?

Most apps will work just fine, but folder virtualization kicks in. For file sharing across the network - that typically won't work unless you create shared folders

>
>Not that I need this for myself - all my stuff is either single user (me) or on SQL - but local guys have questions for me from time to time, and I need to appear as if I know what I'm talking about :). I take it the file sharing paradigm is mostly discouraged, if not deprecated, in Redmond (is SMB3 already out, without ever fixing the SMB2 bug?) and I'm not recommending it to anyone anymore. But from time to time I may need to help the guys who still have to use it.