I work at for a network of offices and we use a remote desktop connection in order to run timeslips from our central office server. The problem is that while a large number of our connections work seamlessly there are a multitude that get the same error when trying to access the database. (I have attached a picture of the error message). At first I believed this was due to the fact that on the computers that were getting this error message they were trying to access the database differently than the other. (for example the correct functioning connection access it through m:\timeslips\ and the others were working through another drive to the shared drive e.g. q:\msshare\timeslips\) I thought that adding a logon script to map the correct drive would correct this but it has not and I still receive the same error. I feel this is an inefficient way to use the program but as it was put in place before I was hired I would prefer to fix this problem before beginning to update and change the existing process.
here is a bit of information that may be of some assistance
- all user profiles are set up the same way as members of three groups (users, power users, and remote desktop)
- all users are configured to run "c:\program files\timeslips\minits.exe" on startup
- logon script correctly maps the drive in which database is stored
- Using Timeslips 2004 version 12.0
installation folder is m:\timeslips\
application folder is c:\program files\timeslips\
database folder is in m:\timeslips\clt\
- Timeslips shows that we have 10 of 13 licenses in use for this database
sorry for the long post , just trying to give as much info as necessary, any help would be appreciated. Is there any easier way to access and use the same database in multiple locations?? or having separate databases for each location and merging them at the server location? (apart from buying a newer version of timeslips with the remote timeslips option)
The problem was in fact the installation folder which at first I could not figure out how to properly configure even with the instructions, It had no change install path command. But I deleted the users and then added them again and browsed to the database on the now correctly mapped drive and it worked like a charm. Thanks for your assistance.