hexagon logo
Register Sign in
  • Replies 21 replies
  • Subscribers 33 subscribers
  • Views 450 views
  • Users 0 members are here
Options
Related

Why is writing to PC-DMIS from VBA so slow?

DaSalo
I have two scripts that do very similar things : Read scan point data from PC-DMIS and then write scan point data back into PC-DMIS. One version of the script is written and executed in PC-DMIS basic. The other is written in Excel VBA and is executed through Excel by calling the macro from a very simple PC-DMIS script.

The PC-DMIS only version writes the scan data out to a temp file and then reads it back out of the file and writes to PC-DMIS. The excel version reads the data out into memory in a 2D array and then writes it back into PC-DMIS from the array, no external files involved.

I figured the Excel version would be faster since everything is in memory. It turns out that it is wicked slow and takes about 11 seconds to write a 64 point scan while the PC-DMIS version does it in less than 1 second. All the time is in the writing via the Puttext method. Reading from PC-DMIS into the array takes a fraction of a second but writing it back out into PC-DMIS takes 11 seconds. In the PC-DMIS only version both operations take a fraction of a second.

Is VBA just inherently slow for this kind of thing? Anyone else experienced this?
Parents
  • I am just writing a collection of utilities that I can use to manipulate scans. I am testing the foundation of this right now on a simple offline program that contains two scans and nothing much else. The script reads the point data from one and then writes it to the other during program execution. That's all.

    Pcdmis is running a script during this time. It is running the script that calls Excel. So it isn't a difference of running a script in pcdmis vs not, it is a difference of which environment is calling which command. Perhaps it is the difference of creating the pcdmis app object through VBA instead of through pcdmis that causes the difference.

    Anyhow, it's working great now so I'm not going to lose any more sleep over it.
Reply
  • I am just writing a collection of utilities that I can use to manipulate scans. I am testing the foundation of this right now on a simple offline program that contains two scans and nothing much else. The script reads the point data from one and then writes it to the other during program execution. That's all.

    Pcdmis is running a script during this time. It is running the script that calls Excel. So it isn't a difference of running a script in pcdmis vs not, it is a difference of which environment is calling which command. Perhaps it is the difference of creating the pcdmis app object through VBA instead of through pcdmis that causes the difference.

    Anyhow, it's working great now so I'm not going to lose any more sleep over it.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement