I've narrowed the problem down a bit, and resloved the worst of it.
Now, if the local app 'sees' an update on a network drive, it copies it to a local folder THEN runs the update executable and releases control by quitting. UAC then fires up and runs the updater as an administrator, and copies the new executable from the (fixed) local folder over the top of the existing app. Here we hit a small snag, the updater then runs the new exe file (as Administrator) and quits (releasing control).
The new exe file is running as Administrator now, so the drive mappings for the data are all wrong, as are all the other personalised settings (printers etc). So, the user must quit the app and reload it manually in Win 7 - I have still to implement that last bit on a live Win 7 installation - but it shouldn't be hard.
Unless someone knows how to force a reversion to the original user?
Regards
Griff
Keep [Smile]ing
There are 10 kinds of people in the world, those who understand binary and those who don't.