Randem Systems Support Board

Still you don't want the exe in an unprotected folder... commonappdata
 
 
Merry Christmas

Yes, I understand {commonappdata} with respect to data but is it the best (or a desirable) place to put BOTH the app and the data, which it seems I have to do to for a network installation?
 
Because of it's All Users aspect it would seem that {commonappdata} would work well from a permissions standpoint.  On the other hand, a simply-named unique folder like GHM would be easier to deal with, both with respect to the app's code (somewhat) and in terms of neophtye users understanding.  What's your preference?
 
I'm off today on a family Christmas trip and will return on Wednesday.  My best wishes to you for a Merry Christmas.  Enjoy the holidays, and thanks again for all your assistance.

That is what the {commonappdata} folder is for... to store your data that is common to all users.

You can still install your app (just like PDW) but in common data folder and it will work but the second explaination still applies.
 
Thanks for the explanation.  It seems that, with the Server Shared App that I have, to do what I want to do from an installation standpoint only (concurrency checking understood from an  execution standpoint) requires that the app and the data be in the same folder (a shared folder).  That isn't a problem with XP (and presumably Win2K).  What I had working previously was with a unique folder separate from Program Files.  I now know that with Vista I can't have both the app and data in the same folder under Program Files.
 
So, the $64K questions for Vista:
1) Can I use my own named unique folder (say GHM) separate from Program Files without running into all the Vista permissions hassles?
 
2) If not, is there a system folder name common to Wink2K, XP and Vista that is usable?  (You might be saying that the {commonappdata} folder is such.)
 
If the answer to both questions is No, it seems like I'll need a separate installation package for Vista (or at least a separate package for newtork use on Vista).  If true, is there a best Vista folder to use?

Your perception of client/server is awry. You cannot easily convert your code to client/server, it has to be designed that way. Two distinctly separate pieces of software.
 
Client/Server - An app that is installed and run on the server (you actually have to go to the server to run it) and the clients connect to it via something like Winsock. The clients send requests to the server app and the server app queues the request then operates on them one at a time in sequence.
 
Server Shared App - App is installed on the server  and shared, but each user runs a copy of the app on their own machine. All the work is done on each users machine and stored on the server in the common shared folder. This can cause all sorts of conflict with the data if not coded properly with concurrency checking.
 
You can still install your app (just like PDW) but in common data folder and it will work but the second explaination still applies.

Also BTW, my last post was not menat to imply that the PDW had anything to do with things.  I think it was the fact that both the data and the app were in the same folder, something that is a no no with Vista.

BTW, back when I was using a PDW Setup and had the app and the data in the same folder, under XP I simply mapped a drive (Z) to servernamesharedfoldername and installed for the Client to just Z: - and that worked.

We start off again with confusion - mine!  Given what you say, two questions:
 
1) If it's appropriate, how do I get the app to be a client/server app?, OR
 
2) Given what I have, how do I retain common data - that is, the data-related actions by the users of all Clients are reflected in a single common set of data files?

The data files are changed by the CLIENT. You do not  have a client/server app. You just have a app that sits on the server and is shared. The app will actually run on each users machine not on the server. Very, Very different...
 
Being that the app will actually run on the clients machine they too need all the dependencies installed on each machine where the app is to be used.

Okay - I'm ready to move on to using InnoScript and Inno Setup to install on Client computers in a network.  Recognizing the wisdom of Occam's Razor, I'm looking for the simplest correct approach.
 
Here's what I have:
-- The app is installed on the Server in Program FilesGHM where GHM is a shared folder.
 
-- The data files used by the app are in a separate Server folder produced in Setup by {commonappdata}GHMDATA.
 
-- I want the Client computers to access the app on the Server and use the data files on the Server.  (The data files are common to all Clients - that is, all Clients use the same single set of Server data files.)  The data files are not changed directly by the Client; they are changed by the app on the Server based on Client input to the app.
 
-- The Setup for the Server includes installation of both the app and some data files.  For the Clients I just want to gain access to the app on the Server with no impact on the Server data files.
 
-- My initial thinking is to use a UNC Path for a Client install - that is, \ServerNamesharename, where sharename is the GHM folder where the app is installed on the Server - and include in the install only the app files.
 
Before I go off and screw things up, some guidance please!  And Thanks.