07-28-2011 07:09 AM
Interestingly, I've just seen this in the manual for ACTDIAG v14 (Page 15)
Set up ACT! SQL Users. Runs the SecurityCmdLnApp used to create the specific SQL accounts
(users) that Sage ACT! requires to function and allow Sage ACT! to connect to the SQL Server
database. You would use this command if you manually created the ACT7 instance, or you set up the
manual instance, and you only want the database and not the Sage ACT! desktop application on the
computer. This command also adds stored procedures to the master database. An output file called
SecurityCmdLnApp.txt is placed on the desktop that shows if the command was run successfully.
I really have no idea what that might allow ... or, if it doesn't run that way, why you'd have the database without the app?
07-28-2011 08:56 AM
Interesting discussion. The way ACT! is designed to work with SQL is to connect to a specific SQK instance called ACT7. In a multi-client setup, the main database must connected to a local SQL Server. The client machines can access this database via the SQL Server Browser service (hosted on the main server). I am not aware that any type of remote access to SQL Server is supported - this is outside of the standard recommended setup. The client machines must be able to access the database, database files, and SQL Server instance via a network (LAN, VPN, terminal services, etc).
In regards to the reference Mike mention regarding SecurityCmdLnApp, it is possible for the server to host a database through SQL without having to install ACT!. This has been tested with mixed success, so it's not yet officially supported. The client machines do not have to have SQL installed on them in order to connect to a shared server instance/database. However, not having a local ACT7 instance means they will not have some functionality available to them. See KB Article 26905 for more information.
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
07-28-2011 09:30 AM