Vista explorer can write to network folder but app can't?

[Mark B]

I have a Microsoft Access database runtime application (split front end/back
end) that normally runs fine with the backend data file (BackendData.mdb)
sitting on a shared network folder.

I have been contacted by a user who says he's getting a 'No permission'
error when the front-end app tries to write to the BackendData.mdb file in
the network folder.

He says however that through the particular machine's Vista Windows
Explorer, he can write (e.g. copy BackendData.mdb, create new documents) to
that network folder OK.

The server is Windows 2003.

How can I give 'my app' permission to write to the network folder?

 

[MBUnit]

I have a Microsoft Access database runtime application (split front
end/back end) that normally runs fine with the backend data file
(BackendData.mdb) sitting on a shared network folder.

I have been contacted by a user who says he's getting a 'No permission'
error when the front-end app tries to write to the BackendData.mdb file
in the network folder.

He says however that through the particular machine's Vista Windows
Explorer, he can write (e.g. copy BackendData.mdb, create new documents)
to that network folder OK.

The server is Windows 2003.

How can I give 'my app' permission to write to the network folder?

I would say that the Access.exe that is used to run the Access VBA
solution by the user must be started with a short-cut that has Run As
Administrator enabled. It could be the case that the Access.exe itself
that runs the VBA solution needs its rights escalated, which is done by
using Run As Administrator on the exe or a short-cut that points to the exe.