Answer My Searches

I started getting this error a few days after upgrading to QBPOS v9.0 when trying to print a sales receipt.

It seemed to fix the issue to backup Point of Sale, uninstall it with add/remove programs, and reinstall POS.

Resources:
http://community.intuit.com/posts/library-not-registered-3
http://community.intuit.com/posts/library-not-registered-error-when-using-pos-90
http://community.intuit.com/posts/library-not-registered-2

I made three new custom search engines to help readers research key issues mentioned on this site. Basically each one is limited to search only within the top 3-10 forums, blogs, and support pages for the topic.

These will save a lot of time since you can now do just one search, instead of having to search every forum every time you have a question.

Here they are. Let me know how they work. I’m also adding them to the Helpful Resources sidebar so you’ll always have an easy link to them.

1. Ubuntu Search (Searching *.ubuntuforums.org, *.ubuntu.com/ )
2. GoldMine Search (Searching *.frontrange.com, *.contactreview.net, *.castellcomputers.com, *.thegmblog.com)
3. QuickBooks Search (Searching *.quickbooksgroups.com, *.intuit.com )

Let me know if you have more resources, or blogs I can add to any of these search engines.

Tip: If you’re working with the QuickBooks API and QuickBooks returns an error message like this:
QuickBooks found an error when parsing the provided XML text stream.

The first thing to think about (assuming your XML generally looks valid) is the ordering of your elements. The XML schema requires all of the XML elements be in a specific order. You can view the order in the OnScreen Reference.

In general to get more information about a XML error, start up your qb* XML Validator tool (should be installed with SDK) and put in your XML file. Here’s the error I got from having an out of order element:
Reason: Element content is invalid according to the DTD/Schema.
Expecting: ServiceDate, SalesTaxCodeRef, IsTaxable, OverrideItemAccountRef.

I tried out QuickBooks Enterprise Solutions 6.0 today in hopes that upgrading from version 5.0 would allow us to have more user defined / custom fields. These let you store extra information for various entities. For example you could store the color of an item, or the tracking number for an invoice. However version 5 and also version 6 limit you to 5 new fields for items and 7 new fields for customers and believe it or not, we are all maxed out.

Here are some screen shots in case you don’t believe me

(more…)

It’s not, NEVER! I suppose it was just a rumor this whole time. I just came across this in the QB forums. It’s a shame because the QuickBooks API is just so slow and cumbersome.

I honestly do not know where the rumour that we are doing a MSSQL Server version of QuickBooks keeps coming from — we’re not. Any plans we may or may not have regarding a database change would not be discussed in public — Intuit does not pre-announce product…

Even if we WERE to do a SQL-based database the SDK would remain the same (and you would not have ODBC access to the DB) because we would want the freedom to change DB schemas without breaking 3rd party applications. You would be best served sticking with the SDK or a layer built on top of it (like qODBC) that lets you focus on your program logic.

————————-
Peter A. Vogel
Developer Support Manager | IDN PM Lead
Staff SW Engineer
Intuit Developer Network

I read this here.

[tags]QuickBooks, QuickBooks API, API, MSSQL Server, QuickBooks Schema, QuickBooks Database[/tags]