Donovan has posted his second article at the Intuitive Accountant, “QuickBooks Custom Reporting – A Series: More about Reporting Tools.” This article covers Xpanded Reports, QQube, QODBC and the Custom Advanced Reporting (CAR) tool. To learn more about these tools have a look at the article, and let us know what you think. Make sure that you’re watching for follow up articles in the series.
Donovan has begun writing a series of articles for the Intuitive Accountant. His first article, “QuickBooks Custom Reporting – A Series: Introduction” can be found here. Donovan will be following up this introduction with future articles on Custom Reporting. Have a look and let us know what you think, then keep an eye out for the follow ups.
Earlier this year Donovan was personally contacted by QuickBooks® expert Joe Woodard, of Woodard Consulting, to present a workshop on Crystal Reports using QuickBooks® Data and QQube by Clearify at this year’s Scaling New Heights Conference at the Walt Disney World Resort in Orlando, Florida. In 2012 Joe was recognized by Accounting Today as one of the Top 100 influencers within the accounting profession. We were honored to receive the invitation from him and the opportunity to present a workshop at the Scaling New Heights Advanced Training Conference.
In order to prepare for the workshop Donovan became a Certified QQube Professional and Alembic is now a Certified QQube Solution Provider. We are excited about this new certification and look forward to working with you to determine how QQube can help you with your reporting needs.
When Donovan returns he looks forward to telling you all about it!
We were recently asked by several different users how the QuickBooks® Custom Reporting Tool interacts with Microsoft Excel and Access. We have found the Custom Reporting Tool to be very helpful and the interaction between it and Crystal Reports is great. However, we have noticed that there is an “issue” in the way that the product works with Access and Excel, which is what we want to talk about today.
The QuickBooks® Custom Reporting Tool works off of a File Based DSN. This means that the connection info is stored in a file which is located in the same folder as the QuickBooks® file. This file contains the “name” of the database that is being referenced. The “issue” is that the database name changes every time QuickBooks® is closed and reopened. For a product like Crystal Reports this isn’t an issue, because Crystal goes out to the file DSN and reads the database name every time it establishes a connection to the data. The Microsoft products work a little differently though.
When you connect Excel or Access to QuickBooks® via the Custom Reporting Tool instead of going out and reading the database name every time, it stores the name in the application the first time you establish the connection. The problem with this is that Intuit is changing that “name” every time you close and reopen the QuickBooks® file. This means you have to “re-link” the data connection every time you want to use the Excel/Access file you created. For example, in Access you have to go to Database Tools > Linked Table Manager and refresh the linked table information. While this is not overly difficult, it is a pain.
If Intuit didn’t change the database name OR if Microsoft didn’t hardcode the database name in the connection then we wouldn’t have a problem… BUT the “issue” is that they do. We have been in touch with the developer at Intuit several times about this issue and at this point they have not made any changes. They have informed us that they are looking into the issue, but we don’t know if or when they will make any changes to the way they handle the database name.
Hope this clears things up a bit on why the “issue” occurs, but unfortunately at this time there is no “good” way to make the two products play nicely with one another.
One of the latest reports we created using the great new Custom Reporting tool in QuickBooks® Enterprise 2011 was a Cash Register Receipt Report that a client requested. This report allows the client to enter a specific date and see the checks that were received for that day, what invoices they paid off, and then what account those checks got deposited into.
We have this report grouped by deposit account number and then by the check number. The report displays the check number, date, and customer along with the payment total and total amount of discounts given for the invoices covered by that check. Additional invoice details from the check such as date, memo, amount paid, discount amount, etc. are displayed as well.
This report will help the client with daily reconciliation of their finances, something very important to their business. If you have a need to have all this type of info all in one place please feel free to contact us. We will be happy to customize this report to make it fit the specific needs of your company, or use this as a starting place to create a whole new report for you.
Please note that this report was created using the QuickBooks® Enterprise 2011 Custom Reporting Tool and Crystal Reports XI.
Email us at email@example.com or call us at 620.454.9222 to discuss your custom reporting needs.
Here at Alembic we pride ourselves on our ability to create custom reports for a wide range of products; and we have just added another tool to our arsenal, QuickBase®. QuickBase® is a great product but is lacking quite a bit when it comes to attractive, printable reports. The ability to create online databases quickly and easily is great. However, a majority of the time we are creating databases from which we need to provide visually appealing output from.
With the use of the QuickBase ODBC driver we can link to your QuickBase® data and create reports using Crystal Reports. We can also use the driver to access QuickBase® data directly from applications like MS Access, MS Excel, MS Word and more.
If you find yourself in the need for such services please contact us today to see how we assist you.
Last week we spent quite a bit of time converting a client from Macola to QuickBooks® Enterprise Solutions 10 and Fishbowl Inventory 2010. We made the switch using several custom developed Crystal reports. These were formatted in a way that they could be exported and used as either .iif or .csv files. If you have ever worked with importing data into either QBES or Fishbowl Inventory you know that this can sometimes be a rather tedious task.
Overall things went rather well. We did however run into a few obstacles, some of which were larger than others. One of the more frustrating obstacles we encountered occurred during the importing of the bill of material into Fishbowl. The problem was that after our import, everything seemed correct, with the exception of the part number not showing up in the part number column. We found this to be a rather big issue. How do we know what parts to pull if the part number is not listed? The really odd thing was that if you clicked on the line item and then off, the part number would appear. Talk about confusing…
Well, after working with the great support folks at Fishbowl we determined that this issue was occurring because we didn’t include the unit of measure in our import file, which I might add is not a required field. So, the lesson learned here was to include as much information as possible when building an import file. You will have less of a chance for error if you do!