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!

faster automation 1

Status
Not open for further replies.

Rcasady617

Programmer
Oct 28, 2004
3
US
if anyone's doing or going to do this i'd enjoy talking to you.
Set System = CreateObject("EXTRA.System")
slow and hard to use sometimes....

try pre-binding
Dim System As New ExtraSystem
fast and less-hard to use sometimes....

wont work for macros but fast for automation.
 
Exactly correct, but don't forget to add a reference to your project.

calculus
 
calculus,
I dont want to sound dum here but what are the advantages to refrencing the project ie(Dim System As New PRJNAME.ExtraSystem)?
 
I don't quite understand your question. Your original note is correct for use in piloting Extra. Early Bound funtions perform better (although in Extra I don't know if there's much value to that), but you also get the advantage of drop down properties and methods depending on the language your using.

The only disadvantage I've found is that the "MoveTo" method does not work with an early bound screen object. I just revert to the sess0.screen.MoveTo property to overcome this.

calculus
 
Calculus,
I've created a program that runs fine on my computer. the program contains a class that acts as a wrapper for extra. the program runs great but when it is installed on computer other than mine it fails. any sugestions?
 
Is the same version of Extra on the other machine? Is it open? Is the program in EB, VB or VBA?

I've run into some problems with version 6.5 and 7.1 not being 100% compatible, but I've been able to work around it by not using a Extra.Screen object. I have to state in every line of code Sess0.Screen....

calculus
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top