hexagon logo
Register Sign in
  • Replies 21 replies
  • Subscribers 33 subscribers
  • Views 459 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
  • Yes WYSIWYG, anytime I need additional info, hit points from an auto circle for instance, I just retrieve the command from PCDMIS and process it (for example: Dim cmd as Command = cmds.Item(cmdName)). It's still pretty fast. You could probably also expand the groups before grabbing the text, and collapse them immediately after? We don't use groups very often.

    As far as binding...I typically always declare as the particular object type (early binding?) and see no difference in speed. I mostly do it because of the auto complete in VS. Slight smile

    Dim cmd As PCDLRN.Command
    Dim cmds As PCDLRN.Commands
Reply
  • Yes WYSIWYG, anytime I need additional info, hit points from an auto circle for instance, I just retrieve the command from PCDMIS and process it (for example: Dim cmd as Command = cmds.Item(cmdName)). It's still pretty fast. You could probably also expand the groups before grabbing the text, and collapse them immediately after? We don't use groups very often.

    As far as binding...I typically always declare as the particular object type (early binding?) and see no difference in speed. I mostly do it because of the auto complete in VS. Slight smile

    Dim cmd As PCDLRN.Command
    Dim cmds As PCDLRN.Commands
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement