NICEBERG wrote on Sep 11
th, 2006 at 1:18pm:
A followup question:
Can we run this app from a mapped drive? The mapped drive would be the server install folder shared. Currently we're running it from the client and don't want to have to continue to update every machine when each new version comes out.
You can run the sesame executable from a mapped hard drive. You will still need to specify the -client flag when it is invoked. Your users may not like having to wait while the Sesame executable is pulled through the net to their machine, every time they start Sesame.
You may consider mapping the client machines's hard drives onto a single machine and using a simple script on that single machine to update the executables on all of the clients.
Quote:Is anyone else running this from a mapped drive? We originally did but then switched to the -client way. We did experience some isssues doing it that way but are wondering if maybe it was related to the version we were on at the time.
Here it sounds like you are talking about mapping the Sesame application (the .db and .dat files). If you do this the server alone will execute the application through file sharing, and be slower because it will need to hit the net to get to its files. The client computers have no access to these files except by going through the Sesame server software, and will be unaffected.
If you try to have multiple clients (running standalone, no "-client" flag) attempt to access the same application files (.db and .dat) on a shared harddrive that they all share, the files will locked for all but the first client. If you unlock the files to allow other clients (standalone) to get to these files, you will absolutely damage the files permanently - destroying your data.