Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Automation Errors 1

Status
Not open for further replies.

jeffg99

Programmer
Apr 19, 2001
3
US
Hello. I'm user-level testing an NT 4.0 Windows-based application written in VB/C++ and have received several "Automation" errors. For example, I've observed "Unable to generate a uuid" and "The data necessary to complete this application is not yet available." In general, are these errors unique to VB? VBA? C++? Are they COM-related? Do they bubble up from the O/S? Thanks.
 

Sounds to me like someone hasn't quite finished writing the application that you're testing...
 
Ahhhh, yes, that is true. However, do these kinds of errors indicate that the application has been poorly architected? Or is it just that the code needs bullet-proofing? Thanks.
 
Just an idea.
It "might" mean that the programmer used early-binding to a different version of the Automation object model than is present on the testing machine (assuming it is a different machine). I use late-binding to avoid such issues with Word.
Microsoft now recommends late-binding because Access 2000 breaks an early-binding program that used earlier versions of Access.
'=====================================
'======================================
"If you are developing an Automation client for both Microsoft Access 97 and 2000, you should not use early binding: late binding is recommended. The Access 2000 object model was modified such that it breaks both binary (vtable) and dispid compatibility. Any client application that uses early or dispid binding to Access 97 might fail to work properly when run against Access 2000."
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top