Author Topic: win32com.client.Dispatch("EA.App") - how to reference 32 bit and 64 bit version?  (Read 2676 times)

roman104

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
  • Right Information - In Right Time - for Right Role
    • View Profile
    • Right Information - In Right Time - for Right Role
Hi All
I have installed EA15 and EA 16 64 bits at the same workplace.
I am performing application backup of MS SQL repositories into EAPX files via method
MyProject.ProjectTransfer(SourceFilePath=MySourceString, TargetFilePath= MyDestinationString, LogFilePath=MyLogFile).
Is there any way how to reference 32 bit version and 64 bits version?
I am planning to switch from EAPX to QEA files and I need to have both version of EA  in parallel for some time until I uninstall EA15.
I am looking for the way how I can in script (in my case in python) to reference "ea.app" 32 bits (EA15) and "ea.app" 64 bits (ea16)
Thank YOu
Roman

Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1137
  • Karma: +30/-8
    • View Profile
Hi Roman,

From memory there is no way to differentiate 32-bit from 64-bit, 32-bit and 64-bit have the same version and build numbers.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Can't you get the application exe path name somehow?

q.

roman104

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
  • Right Information - In Right Time - for Right Role
    • View Profile
    • Right Information - In Right Time - for Right Role
Hi Vega
thank You for confirmation of my assumptions. .
But I have another notebook, where there are the same applications EA15 and EA16, 64 bits. On that second notebook is by default starting EA16 OLE server not EA15 OLE object.
I am not aware How I have got this situation. How the windows knows which is default?
I will be forced to uninstall EA 15 and try once again.




Hi Qwerty,
I am afraid, but I could try it, to put isntead "EA.App" reference to physical file, with ole server.
maybe it could be, but I have no experience with it.
Thank You


Roman

wivel

  • EA User
  • **
  • Posts: 243
  • Karma: +12/-1
  • Driven by Models
    • View Profile
Hi

As far as I recall, it's the one installed last that takes precedence. Something to do with the way components are created in the Windows Registry file.

Henrik

Takeshi K

  • EA User
  • **
  • Posts: 588
  • Karma: +38/-1
    • View Profile
Hello Roman,

I have not tested, but maybe you can choose which EA runs with EA.App after running 'EA.exe /register'. This option updates entries in the Windows Registry.

When you want to run EA 15 by using EA.App, run 'C:\(path to EA 15)\EA.exe /register' then use EA.app. When EA 16,  run 'C:\(path to EA 16)\EA.exe /register' then use EA.app.

Hope this works and helps you.
--
t-kouno

roman104

  • EA User
  • **
  • Posts: 28
  • Karma: +0/-0
  • Right Information - In Right Time - for Right Role
    • View Profile
    • Right Information - In Right Time - for Right Role
Hi All,
I have found the differences which may cause which version of EA.APP (32, or 64 bits) is launched.
The key is client , python version. If I am using 32 bits version its launch the 32  bits version of EA.app.
In case I run the script via 64 bits version of python, it launches  64 bits version of EA.App.


Thank You very much for Your help.
Roman :)