When desktop icons are clicked to open a Sesame database, the file does not open.  Instead we get a message that there are missing files, dat, dst, ddt, or others that are needed.  Response results in having to drill through the normal File/Open branches to get the file, Operations.db that is there, that is not missing anything.  

This is the command line:
C:\Sesame2\Program\sesame.exe -client 700dsr.company.local.:20000:20001 S:\Sesame2\Data\Company\Operations.db -ini_file C:\Sesame2\Utilities\SensibleSolutions\Ini\sesame.ini

This is the Working Directory: C:\Sesame2\

INI files are here: S:\Sesame2\Utilities\SensibleSolutions\Ini\

Server is running on a remote server named 700dsr.company.local.  Server is WIN 2000 SP4.  Workstations are XP-PRO SP3.
All db, dat, dsr, ddt files for Operations application are on that server in S:\Sesame2\Data\Company\ folder
The Server is mapped as Drive S on all workstations.
Client is installed on all workstations in C:\Sesame2\
Using Sesame 2.5.1 on Server and 3 workstations.

This looks like other network installations, but I must be missing a not so obvious typo.  
Who will be FTF (First To Find) the cause of the problem and the final fix?

Thanks Mark.

Quote:
 YES

Hmm, will have to check the rootdirs on the server (and the local drives too.  I just remembered that all drive letters are enabled but don't want that).  

I am not sure if the Server has a mapping to Drive S.  

Thanks for the suggestions...  

May be a few days before I can check/correct.  
No Remote Access yet, will need to travel 200 miles.  Do batch tasking when on site.  

Bob_Hansen wrote on May 6^th, 2010 at 5:39am:


Have you ever tried LogMeIn? It's free and you can have the client install it for you, so you can get access without the drive.  (There's a Pro version that allows file transfers, etc. The Pro version is under $6/month, purchased annually.)

I have access to over 90 computers using LogMeIn. It's very reliable and has plenty of admin functions, even remotely turn on computers.