Note 13 - Recently Issued Accounting Pronouncements	12 Months Ended
Dec. 31, 2012
Accounting Changes and Error Corrections [Text Block]	13. RECENTLY ISSUED ACCOUNTING PRONOUNCEMENTS In December 2011, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) 2011-12, Comprehensive Income (Topic 220), Deferral of the Effective Date for Amendments to the Presentation of Reclassifications of Items Out of Accumulated Other Comprehensive Income in Accounting Standards Update No. 2011-05. This ASU deferred the ASU 2011-05 requirement that companies present reclassification adjustments for each component of accumulated other comprehensive income (“AOCI”) in both net income and other comprehensive income on the face of the financial statements. Companies are still required to present reclassifications out of AOCI on the face of the financial statements or disclose those amounts in the notes to the financial statements. This ASU also defers the requirement to report reclassification adjustments in interim periods. This ASU is effective for interim and annual periods beginning after December 15, 2011 and is to be applied retrospectively. The Company’s adoption of this update did not have a material impact on the consolidated financial statements. In June 2011, the FASB issued ASU 2011-05, Comprehensive Income (Topic 220): Presentation of Comprehensive Income. This update requires that all nonowner changes in stockholders’ equity be presented in either a single continuous statement of comprehensive income or in two separate but consecutive statements. This ASU is effective for interim and annual periods beginning after December 15, 2011 and is to be applied retrospectively. The Company’s adoption of this update did not have a material impact on the consolidated financial statements. In May 2011, the FASB issued ASU 2011-04, Fair Value Measurement (Topic 820): Amendments to Achieve Common Fair Value Measurement and Disclosure Requirements in U.S. GAAP and IFRSs. The amendments in this ASU generally represent clarification of Topic 820, but also include instances where a particular principle or requirement for measuring fair value or disclosing information about fair value measurements has changed. This update results in common principles and requirements for measuring fair value and for disclosing information about fair value measurements in accordance with U.S. Generally Accepted Accounting Principles (“GAAP”) and International Financial Reporting Standards (“IFRS”). The amendments are effective for interim and annual periods beginning after December 15, 2011 and are to be applied prospectively. Early application is not permitted. The Company’s adoption of this update did not have a material impact on the consolidated financial statements. In October 2009, the FASB issued ASU 2009-14, Certain Revenue Arrangements That Include Software Elements—a consensus of the FASB Emerging Issues Task Force, that reduces the types of transactions that fall within the current scope of software revenue recognition guidance. Existing software revenue recognition guidance requires that its provisions be applied to an entire arrangement when the sale of any products or services containing or utilizing software when the software is considered more than incidental to the product or service. As a result of the amendments included in ASU No. 2009-14, many tangible products and services that rely on software will be accounted for under the multiple-element arrangements revenue recognition guidance rather than under the software revenue recognition guidance. Under this ASU, the following components would be excluded from the scope of software revenue recognition guidance: the tangible element of the product, software products bundled with tangible products where the software components and non-software components function together to deliver the product’s essential functionality, and undelivered components that relate to software that is essential to the tangible product’s functionality. This ASU also provides guidance on how to allocate transaction consideration when an arrangement contains both deliverables within the scope of software revenue guidance (software deliverables) and deliverables not within the scope of that guidance (non-software deliverables). The Company adopted and prospectively applied the provisions of this standard beginning January 1, 2011. The adoption of this standard did not have a material impact on the consolidated financial statements.

Note 13 - Recently Issued Accounting Pronouncements

12 Months Ended

Dec. 31, 2012

Accounting Changes and Error Corrections [Text Block]

13. RECENTLY ISSUED ACCOUNTING PRONOUNCEMENTS

In December 2011, the Financial Accounting Standards Board (“FASB”) issued Accounting Standards Update (“ASU”) 2011-12, Comprehensive Income (Topic 220), Deferral of the Effective Date for Amendments to the Presentation of Reclassifications of Items Out of Accumulated Other Comprehensive Income in Accounting Standards Update No. 2011-05. This ASU deferred the ASU 2011-05 requirement that companies present reclassification adjustments for each component of accumulated other comprehensive income (“AOCI”) in both net income and other comprehensive income on the face of the financial statements. Companies are still required to present reclassifications out of AOCI on the face of the financial statements or disclose those amounts in the notes to the financial statements. This ASU also defers the requirement to report reclassification adjustments in interim periods. This ASU is effective for interim and annual periods beginning after December 15, 2011 and is to be applied retrospectively. The Company’s adoption of this update did not have a material impact on the consolidated financial statements.

In June 2011, the FASB issued ASU 2011-05, Comprehensive Income (Topic 220): Presentation of Comprehensive Income. This update requires that all nonowner changes in stockholders’ equity be presented in either a single continuous statement of comprehensive income or in two separate but consecutive statements. This ASU is effective for interim and annual periods beginning after December 15, 2011 and is to be applied retrospectively. The Company’s adoption of this update did not have a material impact on the consolidated financial statements.

In May 2011, the FASB issued ASU 2011-04, Fair Value Measurement (Topic 820): Amendments to Achieve Common Fair Value Measurement and Disclosure Requirements in U.S. GAAP and IFRSs. The amendments in this ASU generally represent clarification of Topic 820, but also include instances where a particular principle or requirement for measuring fair value or disclosing information about fair value measurements has changed. This update results in common principles and requirements for measuring fair value and for disclosing information about fair value measurements in accordance with U.S. Generally Accepted Accounting Principles (“GAAP”) and International Financial Reporting Standards (“IFRS”). The amendments are effective for interim and annual periods beginning after December 15, 2011 and are to be applied prospectively. Early application is not permitted. The Company’s adoption of this update did not have a material impact on the consolidated financial statements.

In October 2009, the FASB issued ASU 2009-14, Certain Revenue Arrangements That Include Software Elements—a consensus of the FASB Emerging Issues Task Force, that reduces the types of transactions that fall within the current scope of software revenue recognition guidance. Existing software revenue recognition guidance requires that its provisions be applied to an entire arrangement when the sale of any products or services containing or utilizing software when the software is considered more than incidental to the product or service. As a result of the amendments included in ASU No. 2009-14, many tangible products and services that rely on software will be accounted for under the multiple-element arrangements revenue recognition guidance rather than under the software revenue recognition guidance. Under this ASU, the following components would be excluded from the scope of software revenue recognition guidance: the tangible element of the product, software products bundled with tangible products where the software components and non-software components function together to deliver the product’s essential functionality, and undelivered components that relate to software that is essential to the tangible product’s functionality. This ASU also provides guidance on how to allocate transaction consideration when an arrangement contains both deliverables within the scope of software revenue guidance (software deliverables) and deliverables not within the scope of that guidance (non-software deliverables). The Company adopted and prospectively applied the provisions of this standard beginning January 1, 2011. The adoption of this standard did not have a material impact on the consolidated financial statements.

- Definition

The entire disclosure for reporting accounting changes and error corrections. It includes the conveyance of information necessary for a user of the Company's financial information to understand all aspects and required disclosure information concerning all changes and error corrections reported in the Company's financial statements for the period.

+ References+ Details