Difference between revisions of "Freeside:1.7:Documentation:Accounting:CrystalReports"
From Freeside
| Line 3: | Line 3: | ||
=== Configure the Freeside backend === | === Configure the Freeside backend === | ||
| − | * Add a PostgreSQL user | + | * Add a PostgreSQL user and set a password |
| − | <code>createuser reports</code> | + | <code>createuser -P reports</code> |
* Grant the new PostgreSQL user read-only access to the freeside tables | * Grant the new PostgreSQL user read-only access to the freeside tables | ||
<code>freeside/bin/pg-readonly ''freeside_username'' reports</code> | <code>freeside/bin/pg-readonly ''freeside_username'' reports</code> | ||
| − | * Allow the new PostgreSQL user access from the | + | * Allow the new PostgreSQL user access from the IP which will be running Crystal Reports. Edit <code>pg_hba.conf</code> and add an access line, for example, for 192.0.2.56: |
| + | <pre> | ||
| + | # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD | ||
| + | host freeside reports 192.0.2.56 255.255.255.255 md5 | ||
| + | </pre> | ||
| + | |||
| + | * Restart PostgreSQL | ||
=== Configure the Crysal Reports client === | === Configure the Crysal Reports client === | ||
Revision as of 20:02, 28 December 2006
Configuring Crystal Reports to access Freeside
Configure the Freeside backend
- Add a PostgreSQL user and set a password
createuser -P reports
- Grant the new PostgreSQL user read-only access to the freeside tables
freeside/bin/pg-readonly freeside_username reports
- Allow the new PostgreSQL user access from the IP which will be running Crystal Reports. Edit
pg_hba.confand add an access line, for example, for 192.0.2.56:
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD host freeside reports 192.0.2.56 255.255.255.255 md5
- Restart PostgreSQL
Configure the Crysal Reports client
- On the machine running Crystal Reports, download and install the current version of the PostgreSQL ODBC driver from http://www.postgresql.org/ftp/odbc/versions/msi/
- Use the PostgreSQL ANSI driver
- Use the username (i.e.
reports) and password you configured on the backend.
