Community
Showing results for 
Search instead for 
Do you mean 
Reply

ACT 2012 Premium - How can we access SQL

New Member
Posts: 4
Country: Hong_Kong

ACT 2012 Premium - How can we access SQL

Our IT is developing the 3rd party database to interface with SAGE ACT 2012. They need some basic information on how to access SAGE backend database and would appreciate if somebody could kindly give some advice:

1. How to access SAGE back end database: User Name and password if there are any, such as "sa" which is default administrator user name or other db user name with admin rights / reading rights at least.
( PS. "User Name" memtioned here does not mean SAGE Application User Name, it means SQL server Database User Name)

2. We have added some customized fields into SAGE, we would like to know the relationship between SAGE customer end screen filed and Sql Server Datafield if possible.

 

We would appreciate very very much, if somebody could help us a little bit, thanks!!!

 

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: ACT 2012 Premium - How can we access SQL

Do you want to read-only or read/write the ACT! data?

For read-only, you can use OLEDB or ODBC with the ActReader utility
For read/write, you need to use the ACT! SDK

You might find this useful:
http://blog.glcomputing.com.au/2009/07/connecting-to-act-by-sage-data.html
New Member
Posts: 4
Country: Hong_Kong

Re: ACT 2012 Premium - How can we access SQL

Thanks for your quick reply and kind help Mike, really apprciate it!

 

We have added in some customized fields into 2012 Premium. Our IT found that the SDK has more than 400 data tables which makes it really difficult for them to find the position of the fields in the 400 data tables where they want to pull data out of SAGE.

 

Do you have any suggestions on this? Thanks again in advance, this will really help us a lot!

 

Regards

Franziska

 

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: ACT 2012 Premium - How can we access SQL

Are you only wanting to read the ACT! database? Then I usually recommend the OLEDB interface