Adoption of Accounting Standards Updates	9 Months Ended
Apr. 30, 2011
Adoption of Accounting Standards Updates
Adoption of Accounting Standards Updates	(2) Adoption of Accounting Standards Updates The Financial Accounting Standards Board's ("FASB") Accounting Standards Codification ("ASC") is subject to updates by FASB, which are known as Accounting Standards Updates ("ASU"). The following are FASB ASUs which have been issued and incorporated into the FASB ASC and adopted by us: On August 1, 2010, we adopted FASB ASU No. 2010-17, which is an update of FASB ASC 605 "Revenue Recognition - Milestone Method: Milestone Method of Revenue Recognition." ASU 2010-17 provides guidance on applying the milestone method to milestone payments for achieving specified performance measures when those payments are related to uncertain future events. The scope of ASU 2010-17 is limited to transactions involving research or development. During the nine months ended April 30, 2011, we did not have any research and development transactions with milestone payments that were covered under this ASU; thus, the adoption of this ASU did not have any impact on our Condensed Consolidated Statement of Operations or financial position. On August 1, 2010, we adopted FASB ASU No. 2009-14, which amends FASB ASC 985 "Software." This FASB ASU indicates that tangible products containing both software and non-software components that function together to deliver the tangible product's essential functionality are no longer within the scope of the software revenue guidance in FASB ASC 985-605. This FASB ASU also requires that hardware components of a tangible product containing software components always be excluded from the software revenue guidance. Our adoption of this ASU did not have a material impact on our Condensed Consolidated Statement of Operations or financial position. On August 1, 2010, we adopted FASB ASU No. 2009-13 which is an update of FASB ASC 605-25 "Revenue Recognition - Multiple-Element Arrangements." In addition to establishing a hierarchy for determining the selling price of a deliverable, this FASB ASU eliminates the residual method of allocation of arrangement consideration and instead requires use of the relative selling price method. Our adoption of this ASU did not have a material impact on our Condensed Consolidated Statement of Operations or financial position.

Adoption of Accounting Standards Updates

9 Months Ended

Apr. 30, 2011

Adoption of Accounting Standards Updates

Adoption of Accounting Standards Updates

(2) Adoption of Accounting Standards Updates

The Financial Accounting Standards Board's ("FASB") Accounting Standards Codification ("ASC") is subject to updates by FASB, which are known as Accounting Standards Updates ("ASU"). The following are FASB ASUs which have been issued and incorporated into the FASB ASC and adopted by us:

On August 1, 2010, we adopted FASB ASU No. 2010-17, which is an update of FASB ASC 605 "Revenue Recognition - Milestone Method: Milestone Method of Revenue Recognition." ASU 2010-17 provides guidance on applying the milestone method to milestone payments for achieving specified performance measures when those payments are related to uncertain future events. The scope of ASU 2010-17 is limited to transactions involving research or development. During the nine months ended April 30, 2011, we did not have any research and development transactions with milestone payments that were covered under this ASU; thus, the adoption of this ASU did not have any impact on our Condensed Consolidated Statement of Operations or financial position.

On August 1, 2010, we adopted FASB ASU No. 2009-14, which amends FASB ASC 985 "Software." This FASB ASU indicates that tangible products containing both software and non-software components that function together to deliver the tangible product's essential functionality are no longer within the scope of the software revenue guidance in FASB ASC 985-605. This FASB ASU also requires that hardware components of a tangible product containing software components always be excluded from the software revenue guidance. Our adoption of this ASU did not have a material impact on our Condensed Consolidated Statement of Operations or financial position.

On August 1, 2010, we adopted FASB ASU No. 2009-13 which is an update of FASB ASC 605-25 "Revenue Recognition - Multiple-Element Arrangements." In addition to establishing a hierarchy for determining the selling price of a deliverable, this FASB ASU eliminates the residual method of allocation of arrangement consideration and instead requires use of the relative selling price method. Our adoption of this ASU did not have a material impact on our Condensed Consolidated Statement of Operations or financial position.