>>>my app and it's data are all on the E: drive away from any windows owned folders
>>
>>The only folders that are not affected by UAC is anything under your user folder on Windows. Anything anywhere else is restricted by UAC permissions... C: drive, E: drive and network drives it doesn't matter. You'll need explicit permissions in those folders and even then Windows will redirect the file output to a temporary location in your users folder, not actually writing the data into the actual folder via file/folder virtualization.
>>
>>If you haven't disabled UAC or you're not running as THE Administrator account you shouldn't store data in any local folders as you'll have a huge performance hit or worse occasional failures to write data as its being virtualized. All application data should be stored somewhere in the user or AppData folders.
>
>Does this mean that file sharing, record locks etc are now officially dead? That under Windows we now have only the choice between user's private data, shared documents and a SQL(like) app on the server?

No, but it does mean out of box you have to set permissions to make that work reliably. The problem with desktop apps is that they shouldn't muck with your computer permissions so a program can install into a Program Files folder and have data there, but it would have to change permissions there to allow the local user to write there directly (w/o FolderVirtualization)...

+++ Rick ---