Google
 

Thursday, March 27, 2008

FRxBUZZ :: The Techie Version of Life's Too Short To Do Balance Sheets in Crystal

FRxBuzz debates Crystal vs. FRx for Financial Reporting.

Why are there two reportwriters (usually Crystal and FRx in the midmarket) when you're implementing a new ERP? Why not just use Crystal to create the financial reports? Crystal is a database reportwriter. The database that contains the accounting transactions can have a couple hundred tables (or more). To create financial reports in Crystal, you would have to know lots of techie things like which tables contain the data you need (and tables can have very strange names!), which field to use to link those tables, how to structure the join that links the tables, the field names for the data you need, and how the application flags items in the database like whether a transaction is posted, how to separate budget from actual, how to exclude void transactions, and a whole host of other things absolutely critical to accuracy.

How do you do that when you’re an accountant without extensive training on this one database? Answer: you don’t. You use FRx instead.

FRxBUZZ :: The Techie Version of Life's Too Short To Do Balance Sheets in Crystal

1 comment:

jlh said...

I changed blog platforms yesterday and all links have changed. Here's a new valid link to my 'techie version' post. Jan Harrigan

http://www.frxbuzz.com/the-techie-version-of-lifes-too-short-to-do-balance-sheets-in-crystal/