Wednesday, June 21, 2006

Two Important Notices: Quickbooks 2006 and AT&T

I'm more than a little bit irritated with these two companies.

AT&T is about to steal your corporate data.

AT&T has updated their privacy and essentially it says that you have none. Further any data that you transmit using SBC/AT&T now belongs to them. Might be time to dump that SBC DSL line.

"While your account information may be personal to you, these records constitute business records that are owned by AT&T; as such, AT&T may disclose such records to protect its legitimate business interests, safeguard others, or respond to legal process." ..... read on...

Details here:


AT&T has issued an updated privacy policy that takes effect Friday. The changes are significant because they appear to give the telecom giant more latitude when it comes to sharing customers' personal data with government officials.

The new policy says that AT&T -- not customers -- owns customers' confidential info and can use it "to protect its legitimate business interests, safeguard others, or respond to legal process."

The policy also indicates that AT&T will track the viewing habits of customers of its new video service -- something that cable and satellite providers are prohibited from doing.

Moreover, AT&T (formerly known as SBC) is requiring customers to agree to its updated privacy policy as a condition for service -- a new move that legal experts say will reduce customers' recourse for any future data sharing with government authorities or others.

Quickbooks 2006 Automatic update coming.

Intuit is pushing out the 7 revision of Quickbooks 2006 this week even though it has a known error. The readme for the document includes the error information. If you get this error after updating Quickbooks, let us know.

Note on Limited Potential Error

You should be aware that in a limited number of cases, installing the R7 update could result in an error message:

Unable to Apply Patch

This error message appeared sometimes in conjunction with Error code 1612 or 1603. In the unlikely event that you encounter this error, please use these instructions to resolve:

This is the Knowledge Base article that includes the instructions to resolve the problem.


Post a Comment

<< Home