up vote 0 down vote favorite
share [g+] share [fb]

I already posted this question on Stack Overflow here, and I've been advised that it should be on serverfault.

So here's what's this is all about :

I'm wondering how the Windows 7 VirtualStore is working in order to get my Access 2010 app working the same way it used to work in Access 2003. This app's first feature is to get files from FTP and save it in the root of the drive C. It was originally made to work on Access 2003 under Windows XP.

Since I've updated my OS to Windows 7, but keeping Access 2003, the files were saved in the VirtualStore, so no problem here, all is working.

Since I've updated too Access to get the 2010 version, this isn't working anymore. The write just fails, and nothing else happens.

I was told that apps that don't get the proper manifest for UAC get automatically redirected to the VirtualStore, so it seems that's what happens with Access 2003. But in Access 2010, it just fails, not even a popup from the UAC prompting for writing rights.

So, is there a way to get this feature working ? I know that I can tell to write directly in the VirtualStore location, and that I shouldn't write to the C: root. This is just in order to know the way this mechanism is working and how to get this feature correctly working.

By the way, I'm wondering if it's because I use the wininet.dll API's. The failing writing function is wininet.dll's FtpGetFile. Here's my function call :

FtpGetFile(ftp_ok, nomf, "c:\" & nomf, False, 0, &H0, 0)

I'm using Windows 7 Pro 7600 64 bits, Access 2010 14.0.6023.100 32 bits and IE 8.0.7600.16385

link|improve this question
I tend to think you were wrongly steered here. This is for an app that you've written in Access? Doesn't really sound like server admin material to me. – mfinni Jan 12 at 14:46
feedback

1 Answer

up vote 0 down vote

To take a crack at it, what happens if you instead try to write the file to a location that you should definitely be able to write to without UAC, like the desktop of the running user?

link|improve this answer
There's no problem at all writing to the desktop of the running user. I tried another location unprotected by UAC, and it works well too. – Canou Jan 12 at 14:57
So what's wrong with using a known-working destination instead of c:\ ? – mfinni Jan 12 at 15:28
Nothing's wrong doing this of course, and that's what I must be doing. As I stated in my first post, I just wondered what's wrong with Access 2010 since Access 2003 got the right behavior, writing in VirtualStore. It's purely informative, forgive me if it doesn't seem to be on first sight. – Canou Jan 12 at 15:35
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.