We don’t officially support this, but you can do this if you have the appropriate skills with databases and/or reports, or can find somebody to help you. Some more technical information is below.

inFlow uses a Microsoft SQL Server database as a back-end database. You can connect to this using Crystal Reports or some other reporting tool to create custom reports. It creates an SQL Server instance named INFLOWSQL on the server machine. You can log into this using the sa account. The password for the saaccount is the Server Password, which you can find by switching inFlow to multi-user mode and selectingChange Connection from the File menu. You can also connect to this database using an ODBC connection. In fact, there may have been an ODBC connection called local-sql­ created for you after installing inFlow.

Some warnings about this – we don’t officially support connecting to the database outside of inFlow, although we’ll informally be glad to help you get started. Making changes to the database outside of inFlow may lead to unexpected problems. Also, many of the update patches for inFlow will update the database, so if you create some tools that rely on a particular database structure, you should be careful when choosing to update inFlow.

Here’s how to create the ODBC connection if one wasn’t created for you.

1. Open the ODBC window at Control Panel -> Administrative Tools -> Data Source (ODBC)
2. Create New Data Source, and select SQL Server
3. Give it any name and description. The server will be .inFlowSQL (you may also use SERVERNAME/inFlowSQL instead).
4. Use SQL Server authentication. The default login is “sa” and use inFlow’s Server Password as the password
5. Change the default database to “inFlow”.

For more detailed information please see this article on the database schema for inFlow.