John,

The first thing you have to know about clients/server setup for your app is
that it will enable to be run :
as a stand alone one machine for clients with only one machine - use server
installation
your app will be "able" to work like this because all files (app-dll's-data
etc are on the machine)

I am not quite as categorical as Friederich is about registering files or
shortcuts on a "server" machine as this enables the one machine clients to
use the same installer if all is done on the "server" machine

Now imagine you have a one machine client - he needs all shortcuts etc
Now imagine you do a real server install, why refuse any user to work on
that machine if no shortcuts etc ?

THE difference is in size of companies and on definition of "server" - as
Friederich said you can call a server a W95 machine.

In small lans - I presume there will be one machine dedicated to Internet
and your application and data files - client machines will connect to this
machine to access Internet (before you jumped in) and they will also connect
to your app same way

Now - nothing prohibits anyone from using that machine to access your app
exccept some rules written in golden sand in the desert of computing world
IF they know what they are doing (they generally do not)

So I would suggest in your installer "server" side to add a checkbox for
shortcuts etc .... like this give users with two machines the possibility
not to have to buy a third one just because some people will say : never
work on a server! stupid !

For many small apps a "server" is simply a machine were app and data is
stored and accessible on the lan - point.(wether it is a W95 or a W2008 ent
machine with 4 quad core cpus and 32 Gb Ram) so go for the full install
possibility on the servers

Then on client machines all you need is to have shortcuts pointing to the
server installation - DONE BEFORE any CLIENT one of course
So in client install all you need is to get the user to go on the lan and
pick out the correct directory on the "server" machine were YOUR exe has
already been installed
Then to create all shortcuts etc...locally using SB_INSTALLDIR as reference
(server directory) - abit tricky but some try and try will get you what you
need

Prohibit any installation client side if there is no server side install
(allow selection ONLY of YOUR exe over the lan)
Write on client machine in registry the lan directory (user selected it so
it exists) and you might need it "locally"

You can - at this stage do any registry setups also for usernames on the lan
(or do it from your app if left(path,2)='\\' ) - this means UNC dir so lan

Attached is my sebup builder I use for both installs (I do not use checkbox
possibility for server shortcuts - I just install them)

ALL depends on your clients and your app : either go for such a small mixed
installer giving you possibility to do all in one or go for a real server
client install but then you will have the funds available to pay Bill Gates
himself to come and do it for you no ? <BG>

JP





--
Merci - Thank you

JP