06-05-2010 07:04 PM
I am going to be converting from Goldmine to Act!2010. I am a single user, and will be using LogMeIn Pro when I want to work from home, rather than syncing.
I need to also start using TrueCrypt, to add HIPAA-necessary protection. I won't be encrypting the whole drive, just certain folders. Should I encrypt the whole Act program, or just the database folders?
06-14-2010 07:50 PM
I've successfully been using ACT and TrueCrypt for several years.
1. You only need to put the databases (and sub-folders) in the TrueCrypt volume.
2. I have found that the ACT SQLinstance must be restarted after you have booted the TrueCrypt volume.
3. ACT and TrueCrypt behave well together and I've experienced no problems running them in tandem since 2006.
Here's how I do it:
1. Boot the system.
2. Launch TrueCrypt and mount the encrypted volume.
3. Restart the ACT SQL instance. I have a batch file which contains the following code:
NET STOP MSSQL$ACT7
NET START MSSQL$ACT7
4. Start ACT and login to the database hosted on the encrypted volume.
When shutting down:
5. Exit ACT.
6. Stop the ACT SQL instance by RUNning NET STOP MSSQL$ACT7. (I created another batch file with the code to make it easier to run.)
7. Dismount the TrueCrypt volume.
8. Exit TrueCrypt.
9. Power down the computer.
TrueCrypt works and the security is solid.
Greg
06-14-2010 12:33 PM
Act! hasn't been tested with any encryption programs and we wouldn't recommend it. The main question is: would TrueCrypt allow the SQL program access to the database files? If there are any options within TrueCrypt to allow this, they would need to be set up. Before setting it up to encrypt the Act! database I recommend that you create a backup of your database (within Act! > File > Backup > Database) just in case the encryption were to cause corruption.
If you install Act! and create your database using the default settings, there would be no need to encrypt the 'Program Files\Act' folder. There is no 'data' retained within that folder, it is strictly program files.
06-14-2010 01:07 PM
I have posted a message on TrueCrypt forum asking about this. Unfortunately, I am not experienced with SQL and don't really understand it.
I can't imagine that I would be the only ACT user needing encryption, esp with so many real estate and other professionals with financial information in their databases. I need to encrypt this for HIPAA reasons.
Thanks; hopefully I'll find out how to do this.
06-14-2010 01:43 PM
06-14-2010 04:53 PM
06-14-2010 07:50 PM
I've successfully been using ACT and TrueCrypt for several years.
1. You only need to put the databases (and sub-folders) in the TrueCrypt volume.
2. I have found that the ACT SQLinstance must be restarted after you have booted the TrueCrypt volume.
3. ACT and TrueCrypt behave well together and I've experienced no problems running them in tandem since 2006.
Here's how I do it:
1. Boot the system.
2. Launch TrueCrypt and mount the encrypted volume.
3. Restart the ACT SQL instance. I have a batch file which contains the following code:
NET STOP MSSQL$ACT7
NET START MSSQL$ACT7
4. Start ACT and login to the database hosted on the encrypted volume.
When shutting down:
5. Exit ACT.
6. Stop the ACT SQL instance by RUNning NET STOP MSSQL$ACT7. (I created another batch file with the code to make it easier to run.)
7. Dismount the TrueCrypt volume.
8. Exit TrueCrypt.
9. Power down the computer.
TrueCrypt works and the security is solid.
Greg
06-14-2010 09:17 PM
06-15-2010 05:38 AM - edited 06-15-2010 05:43 AM
Just a note about the instructions: it sounds like 'GregH' is using either Act! 2005 or 2006 - so the SQL service is named 'MSSQL$ACT7'. In later versions (2007 through current) the service name is 'SQL Server (Act7)'.
Command syntax example: Net Stop "sql server (act7)"
Note: You will need the double quotes and spaces.
06-15-2010 08:48 AM
06-15-2010 10:05 AM
Greg, I'm running ACT! 2010 ver 12.1.181.0 Hot Fix 1.
I checked the code execution and when I enter NET STOP MSSQL$ACT7 the system responds by stopping the SQL Server (Act7) instance. I then entered NET START MSSQL$ACT7 and the system started the SQL Server (Act7) instance! It is interpreting the old code for the new. (I have, however, now updated my batch files with the newer command syntax.)