InDesign 2024 starts with "CreateObject("InDesign.Application.2023")" in an environment where 2023 and 2024 coexist.
Reproduction steps
1. InDesign 2023 (18.x) is installed on Windows
2. Install InDesign 2024 (19.0) there.
3. Run the following code in VBScript.
Set myInDesign = CreateObject("InDesign.Application.2023")
Expected result
InDesign 2024 (19.0) will start.
Actual result
InDesign 2023 (18.0) will start.
cause
InDesign 2024 installer is overwriting the 2023 registry.
\HKCR\CLSID{231441AB-8969-4F6D-8CD1-B596C4047898}
is the registry for InDesign 2023, but the InDesign 2024 installer has rewritten the contents to InDesign 2024. The same goes for related registries.
CS5 omachi
shared this idea
The fix of the issue is now available in the latest InDesign 2024(v19.0.1.205). We recommend you upgrade to the latest version for the fix.
If you are unable to see the update, go to the Creative Cloud application and click on the context menu on the top right and click on Check for App Updates.
—
Adobe InDesign Team
-
Bev
commented
It looks like this is fixed in 19.0.1.205.
-
JeffK
commented
This is quite problematic in our environment as well - where we typically need to keep multiple versions of InDesign installed, and we interact with them using scripts/custom software. Previous ID versions all have their own unique ID.
-
Fourteen commented
InCopy has this same problem.
-
Dan Korn commented
This is an issue for my company as well. We develop an InDesign plug-in and rely on a unique location in the Registry denoting the location of each version of InDesign to install the appropriate plug-in for that version. The same Registry location being used for two different versions of InDesign makes it impossible to install our plug-in to both.
-
Heidi Rosendall
commented
I have many jobs that have a long completion time. It is important that the InDesign version not change in the middle of the job. It is NOT helpful to me to have an older job all of the sudden open in a newer version or a newer job fail to open because the older version is being used.
InDesign has had a problem with this for some years now - unable to recognize and allow for my choice of version. It hasn't been fixable many times unless I uninstall the version I don't currently want and this is very inconvenient. My support person tells me the problem hasn't gone away and though I don't understand the technical details, I very much NEED access to my version choice on a per publication basis and can work on 4 publications in one day with varying versions due to length of time in process. I also like to try out your beta software but when it opens when I don't want it, that is a problem that makes me reluctant to make it part of my day. -
Bev
commented
I agree with the basic gist of this bug report. However, I think the description is a little backwards. When I use the command
CreateObject("InDesign.Application.2023")
my expected result is
InDesign 2023 will start
my actual result is
InDesign 2024 starts. -
CS5 omachi
commented
I had left out something important.
I've provided a VBScript example to give a clearer example, but this is not something you would run from the Script panel (there is no problem if you run it from the Script panel).
When running from outside InDesign. This means that all programs that use VBA, Python, or other COM objects to interact with InDesign externally are affected.