hexagon logo
Register Sign in
  • Replies 10 replies
  • Subscribers 31 subscribers
  • Views 132 views
  • Users 0 members are here
Options
Related

OLE automation error between 2013 MR1 SP5 and 2014 SP1

Moolvie
I am currently using 2013 MR1 SP5. I have several automation scripts i've been running for years, I installed 2014 SP1 on my CMM to prepare to start using it but apart from it opening the first time after installing, I haven't used it. I am still using 2013 to run the CMM. The issue is the now my BAS scripts won't run in 2013. I started up 2014 and the BAS program will run fine there, it just will not run in 2013 any more the ole automation error I get is at line 6 in my Bas Program which is this line 

Sub Main()
Dim PCDApp, PCDPartPrograms, PCDPartProgram, PCDCommands, PCDCommand As Object
Dim Partnumber, Partname, Supplier, Count%, ECount%, TextLine, EmpList$ ( ), EmpNum% ( ), MachName$ ( ), MachNum% ( ), last$
Dim strPrgName$, strNewName$, strNoExt$, strPath$, FindDot

[B][I][U][COLOR="#FF0000"]Set PCDApp = CreateObject("PCDLRN.Application")[/COLOR][/U][/I][/B]
Set PCDPartPrograms = PCDApp.PartPrograms
Set PCDPartProgram = PCDApp.ActivePartProgram
Set PCDCommands = PCDPartProgram.Commands


this is the first time an upgrade has affected my basic scripts. I don't have a problem using 2014 on the CMM as I do 98% of my programming offline and the software isn't used for all the newfangled programming stuff they've put in.

But my question is, why. and can I fix it so I can still run older versions of PC-DMIS if I choose.

I have a ticket started on this issue.
Parents
  • see, I thought that was the problem, up until we got our new IT service, the account was administrator. It is not now, although it belongs to the admin group. I first noticed it had changed when the auto updater showed SP5 was available and I couldn't download it and had to log out and log in as local admin to install 2013 MR1 SP5. Even then the script worked, but once I installed 2014 MR1 it stopped working.

    I've started a ticket and I am waiting for Hexagon to explain. I've also notified my computer guy here ( not the IT service) again about the admin situation. maybe someone will have another answer before I have to take it upon myself to muck around in the registry.
Reply
  • see, I thought that was the problem, up until we got our new IT service, the account was administrator. It is not now, although it belongs to the admin group. I first noticed it had changed when the auto updater showed SP5 was available and I couldn't download it and had to log out and log in as local admin to install 2013 MR1 SP5. Even then the script worked, but once I installed 2014 MR1 it stopped working.

    I've started a ticket and I am waiting for Hexagon to explain. I've also notified my computer guy here ( not the IT service) again about the admin situation. maybe someone will have another answer before I have to take it upon myself to muck around in the registry.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement