Has anyone set up Peachtree to be accessed both through Terminal Services and by computers accessing the data files directly through a mapped drive to the Peachtree database on the terminal server?
I have users at the server location mapping to the Peachtree database on the server (using S: as the mapped drive). I now want to add remote users with Terminal Services. I have the instructions from dev.remotenetworktechnology.com/ts/peachtree.htm. I am concerned that changing the trnfile on the server to trnfile=W:\windows\ will interfere with the connection between Peachtree and and the computers mapped to the S: drive.
Do I need to set the rootdrive of the mapped computers to W:, copy the .ini file to the user's windows directory and then just set the data path in the .ini file to S:?
Besides not changing what the user's are used to, is there any advantage to having the local computers use a mapped drive instead of just converting them to using terminal services just like the remote computers?
Thanks for your help
Betty
I have users at the server location mapping to the Peachtree database on the server (using S: as the mapped drive). I now want to add remote users with Terminal Services. I have the instructions from dev.remotenetworktechnology.com/ts/peachtree.htm. I am concerned that changing the trnfile on the server to trnfile=W:\windows\ will interfere with the connection between Peachtree and and the computers mapped to the S: drive.
Do I need to set the rootdrive of the mapped computers to W:, copy the .ini file to the user's windows directory and then just set the data path in the .ini file to S:?
Besides not changing what the user's are used to, is there any advantage to having the local computers use a mapped drive instead of just converting them to using terminal services just like the remote computers?
Thanks for your help
Betty