Network Install Data Path

[NewsArchive]

Hi All,

I'm looking for opinions/advice on an installation I'm working on.
This program is a client server SQL based program but there are a number of
INI and data files that are kept on the server.
Traditionally, these files are stored in a Data sub-folder beneath the main
executable folder.
The program is installed to the \Program Files folder on the network
server.
A network share is created to the \Program Files\MyApp folder.
The workstations run the program with the start-in folder as the network
share (usually mapped to a drive).

What are the Vista/Server 2008 ramifications of using a Data folder inside
the Program Files structure when the files are being accessed from another
workstation?

TIA,
Rick

[NewsArchive]

If you ever get it working on UAC machines, then you're still asking
for trouble when MS decides to do whatever.


Jeff Slarve

[NewsArchive]

> If you ever get it working on UAC machines, then you're still asking
> for trouble when MS decides to do whatever.
>

Hi Jeff,

This is a serious request. I can't imagine it is that unusual that a
network installed application needs access to some data files for all
users.

Does anyone know if there is a standard regarding any special folders on
the network server when accessing the server from a workstation?

Thanks,
Rick

[NewsArchive]

Of course, it was serious. UAC doesn't allow write access to Program
Files folders, without elevation.

As far as a "standard" place, IT people do things pretty much their
own way and don't give us (as a vendor) a whole lot of choice in the
matter.

With our application, we let them know that our app needs full write
access for every user, and they put it where they want.

We keep our TPS data folders underneath the main application.

>
>This is a serious request. I can't imagine it is that unusual that a
>network installed application needs access to some data files for all
>users.

Jeff Slarve