07-19-2018 02:54 AM
Our IT people have a general question about installing Act. They want to install Act on a PC with C: and E: partition where the operating system resides on C: and Act will be installed on E: whereby it is NOT necessary for Act to write anything to the C: drive.
07-19-2018 06:30 AM
You can install Act! on another drive but you must use the "Custom" installation method. Using this option lets you change the install directory.
If not needing SQL on the machine as you are going to connnect to the database on the server you can untick to install it.
This may help KB38867
07-19-2018 09:03 AM
07-20-2018 01:20 AM
07-21-2018 03:54 AM
Just in case it is all getting too complicated this is what IT maybe are simply looking to do.
Install ACT on C drive and Databases on another partition so data is only written to and from the partition drive.
This is a fairly normal ACT installation, Install ACT with default options on the server or PC and the create your database on the partition drive.
Worth checking to see if this is in fact what they are wanting to do.
07-23-2018 04:47 AM
Thanks for all the advice.
We have a related questions which concerns the paths to the LNK files (and outlook messages) . They all point to the current location of the messages and LNK files on a local drive with even the PC name in the path.
If we install Act on a different drive on a different machine and we restore the current database on the new drive how do we update the location of the LNK and message files?
07-24-2018 02:47 AM
07-24-2018 05:22 AM
The problem is that the location of the LNK files is currently on a local PC and we would like to get rid of this situation. When I look in ACT under the documents tab I see full paths: <computer name>\databasefiles\attachments\xxxxxxxxxxxxxx.LNK for instance. This means, I believe, that when we install Act on a server we must keep access to this PC open in order to be able to open documents via the designated LNK file.
The documents themselves are stored on a network drive on our server but we still need the local LNK file to make a connection.
The path to the LNK file is stored in the Act database I assume but is there a way to update this 'path' field?
07-24-2018 06:17 AM
07-25-2018 12:33 AM
Thank you but this does not answer my question.
The LNK files are indeed pointing to documents on a network location but Act points to a local machine to connect to the LNK file itself. (see attached png file) The problem is that when we restore a database in act that has been installed on a network drive the paths to the LNK files are all wrong.