installing to network drive

In article <gQdAXo2kIHA.1688@news-server>, rnewman@mindspring.com 
says...
> I have a Plus app that I want to install in a network drive and have it
accessible to many users. It seems that Inno part of the Project Manager insists
on putting the Plus runtime and BDE admin files on the workstation from which
the program is installed, unless I have missed something.  Is the proper
solution simply to add lines to the iss file direction the runtime files to the
\app directory on the network drive?
> 
I think you need to install the runtime and BDE on the work station.  
That's how I've always done it (Post Visual DB 5.6).  


You might be able to do a complete network install but I've never tried 
it.  I think The BDE and Runtime will have registry entries pointing to 
their locations so as long you always have the same mapped drive 
available it may work.  I'm not sure what will happen when multiple 
users run the installed apps, or what sort of performance hit you'll 
take.

-- 
Paul Van House
remove "_removeme_" for e-mail replies
Radio/TV Software and Baseball Stat Software: 
http://www.binxsoftware.com
Radio photos, bloopers, and audio cuts: 
http://www.binxsoftware.com/radio/radiodaze.htm

Paul Van House Wrote:

> In article <gQdAXo2kIHA.1688@news-server>, rnewman@mindspring.com 
> says...
> > I have a Plus app that I want to install in a network drive and have
it accessible to many users. It seems that Inno part of the Project Manager
insists on putting the Plus runtime and BDE admin files on the workstation from
which the program is installed, unless I have missed something.  Is the proper
solution simply to add lines to the iss file direction the runtime files to the
\app directory on the network drive?
> > 
> I think you need to install the runtime and BDE on the work station.  
> That's how I've always done it (Post Visual DB 5.6).  
> 
> 
> You might be able to do a complete network install but I've never tried 
> it.  I think The BDE and Runtime will have registry entries pointing to 
> their locations so as long you always have the same mapped drive 
> available it may work.  I'm not sure what will happen when multiple 
> users run the installed apps, or what sort of performance hit you'll 
> take.
> 
> -- 

I think you are probably correct on this, Paul. The only inconvenience is that
it must then be installed from each workstation that will use the application.

In article <SITPPQClIHA.1688@news-server>, rnewman@mindspring.com 
says...
> Paul Van House Wrote:
> 
> > In article <gQdAXo2kIHA.1688@news-server>,
rnewman@mindspring.com 
> > says...
> > > I have a Plus app that I want to install in a network drive and
have it accessible to many users. It seems that Inno part of the Project Manager
insists on putting the Plus runtime and BDE admin files on the workstation from

which the program is installed, unless I have missed something.  Is the proper
solution simply to add lines to the iss file direction the runtime files to the
\app directory on the network drive?
> > > 
> > I think you need to install the runtime and BDE on the work station. 

> > That's how I've always done it (Post Visual DB 5.6).  
> > 
> > 
> > You might be able to do a complete network install but I've never
tried 
> > it.  I think The BDE and Runtime will have registry entries pointing
to 
> > their locations so as long you always have the same mapped drive 
> > available it may work.  I'm not sure what will happen when multiple 
> > users run the installed apps, or what sort of performance hit you'll 
> > take.
> > 
> > -- 
> 
> I think you are probably correct on this, Paul. The only inconvenience is
that it must then be installed from each workstation that will use the
application.


Bob,

That's true. What some people do is install a basic startup program (and 
the BDE/runtime) on each client PC. Then they take advantage of DEO and 
place all the program objects in a folder or folders on the server to 
which the app.INI file points. This means that future changes to the 
program only require you to update the folders on the server. It would 
not be necessary to reinstall to all the PCs. The downside is that it 
may (but not necessarily) take a little bit longer to initially load the 
program, depending on your network.

A variation of this is to install just the BDE/runtime on the client PCs 
and put the whole program on the server. Users would then just have a 
Windows shortcut to the application that they would click to run it. If 
this is one large .EXE then you will definitely see a delay when you 
first load it. But, it can work for small programs. Depending upon how 
you implement temporary files/tables (if you create any), this technique 
can be a problem because the folder of the app.EXE is often the place 
where a lot of those things end up by default. As well, it can be a 
network admin's headache because this technique requires all users to 
have full rights to the folder.

-- 
Geoff Wass [dBVIPS]
Montréal, Québec, Canada

.|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
.|.|.| ---------------------------------------------------------- |.|.|.

Thanks, Geoff. I think I prefer the second suggestion as the least problematical
for our circumstances.

Geoff Wass [dBVIPS] Wrote:

> In article <SITPPQClIHA.1688@news-server>, rnewman@mindspring.com 
> says...
> > Paul Van House Wrote:
> > 
> > > In article <gQdAXo2kIHA.1688@news-server>,
rnewman@mindspring.com 
> > > says...
> > > > I have a Plus app that I want to install in a network drive
and have it accessible to many users. It seems that Inno part of the Project
Manager insists on putting the Plus runtime and BDE admin files on the
workstation from 
> which the program is installed, unless I have missed something.  Is the
proper solution simply to add lines to the iss file direction the runtime files
to the \app directory on the network drive?
> > > > 
> > > I think you need to install the runtime and BDE on the work
station.  
> > > That's how I've always done it (Post Visual DB 5.6).  
> > > 
> > > 
> > > You might be able to do a complete network install but I've never
tried 
> > > it.  I think The BDE and Runtime will have registry entries
pointing to 
> > > their locations so as long you always have the same mapped drive

> > > available it may work.  I'm not sure what will happen when
multiple 
> > > users run the installed apps, or what sort of performance hit
you'll 
> > > take.
> > > 
> > > -- 
> > 
> > I think you are probably correct on this, Paul. The only inconvenience
is that it must then be installed from each workstation that will use the
application.
> 
> 
> Bob,
> 
> That's true. What some people do is install a basic startup program (and 
> the BDE/runtime) on each client PC. Then they take advantage of DEO and 
> place all the program objects in a folder or folders on the server to 
> which the app.INI file points. This means that future changes to the 
> program only require you to update the folders on the server. It would 
> not be necessary to reinstall to all the PCs. The downside is that it 
> may (but not necessarily) take a little bit longer to initially load the 
> program, depending on your network.
> 
> A variation of this is to install just the BDE/runtime on the client PCs 
> and put the whole program on the server. Users would then just have a 
> Windows shortcut to the application that they would click to run it. If 
> this is one large .EXE then you will definitely see a delay when you 
> first load it. But, it can work for small programs. Depending upon how 
> you implement temporary files/tables (if you create any), this technique 
> can be a problem because the folder of the app.EXE is often the place 
> where a lot of those things end up by default. As well, it can be a 
> network admin's headache because this technique requires all users to 
> have full rights to the folder.
> 
> -- 
> Geoff Wass [dBVIPS]
> Montréal, Québec, Canada
> 
> .|.|.|        dBASE info at http://geocities.com/geoff_wass       |.|.|.
> .|.|.| ---------------------------------------------------------- |.|.|.
> .|.|.|             IT Consultant http://Geoff_Wass.com            |.|.|.