This question is locked. New answers and comments are not allowed.
Hi,
I'm facing an issue where Visual Studio crashes when I set an association between two metamodel class, where one of these classes derives from another metamodel class. If I set the association with the super class, it works fine.
The classes are:
- IEntity (interface)
- Profile (superclass)
+ MaleProfile (subclass)
+ FemaleProfile (subclass)
- AcquiredCommand (class)
I'm setting an association between AcquiredCommand and MaleProfile (only MaleProfiles should have a list of AcquiredCommands).
Right now to avoid crashing Visual Studio I have to set the association between AcquiredCommand and the superclass Profile, but this is not desirable because FemaleProfiles should not have a list of AcquiredCommands (makes sense? :-)).
Please find attached 2 screenshots. To download a stripped down version of the project to demonstrate the issue see: http://thedutchpirates.com/downloads/code/20110126-open-access-crash-project.zip
Hope anyone can help.
Regards,
Skywalker
I'm facing an issue where Visual Studio crashes when I set an association between two metamodel class, where one of these classes derives from another metamodel class. If I set the association with the super class, it works fine.
The classes are:
- IEntity (interface)
- Profile (superclass)
+ MaleProfile (subclass)
+ FemaleProfile (subclass)
- AcquiredCommand (class)
I'm setting an association between AcquiredCommand and MaleProfile (only MaleProfiles should have a list of AcquiredCommands).
Right now to avoid crashing Visual Studio I have to set the association between AcquiredCommand and the superclass Profile, but this is not desirable because FemaleProfiles should not have a list of AcquiredCommands (makes sense? :-)).
Please find attached 2 screenshots. To download a stripped down version of the project to demonstrate the issue see: http://thedutchpirates.com/downloads/code/20110126-open-access-crash-project.zip
Hope anyone can help.
Regards,
Skywalker