List of incompatible software with the Opencities Map connect edition.

Hi Manuel,

can you please provide any example, what do you mean by "incompatible software"?

I am not aware of any such list and I am not even imagine what such list can contain. Maybe an explanation how you plan to use such list can help.

With regards,

  Jan

Good morning Jan Šlegr,

First of all thank you very much for your quick response.

With the list of incompatible software I mean the installation of the product. We have detected that when we install Corel Draw 2020 it has a Visual Basic component called Visual Studio Tools For Aplication 2019 that means that when we use Opencities a Visual Basic error is indicated, which is resolved by repairing that component.

We wanted to know if there is a DB with incompatible software or that interferes with the operation of the product.

Thank you very much and greetings.

Manuel Navarro García said:

We wanted to know if there is a DB with incompatible software or that interferes with the operation of the product.

As I wrote already, I think no such database exists, but I recommend to create Service Ticket and to ask Bentley support team.

Manuel Navarro García said:

that when we use Opencities a Visual Basic error is indicated, which is resolved by repairing that component.

I think you identified the only (or at least the biggest and most often) threat that exists: When another application corrupt MicroStation VBA. I am not sure whether it's the problem of MicroStation, but VBA itself, because installed by many application, is not very robust application. My feeling is that when the application installer is not prepared right, it can easily corrupt VBA in other software.

With regards,

  Jan

This is a good question Manuel, thank you for asking.

While Bentley does not keep a list of 'incompatible' software like the one you are looking for, the Known Issues section in the Map README file contains some information about the current release that you should take into consideration. That is where I would look first for issues like this.  README files are published on the Documentation server, and you can use this link to see the Map README.

A list of component versions used to 'build' the product is maintained by the Development staff, but that list is not published; and there isn't a VBA item listed in it.  I would think that a list of 'incompatible products' for any software could be an open-ended, unending list - 64-bit versions are incompatible with 32-bit versions, Licensing models change so generational versions can be incompatible, & as you note a component may be incompatible between versions.  I am glad to hear the using the Repair option resolved the issue for you.