Thanks so much for your clear explanation. I was not aware of shortcuts, which is definitely helpful.
Nevertheless, I am still not seeing how this solves our needs. My model is over 100 tables in size, and it seems like your tool forces everyone to work with a view that is always 100 tables in size.
Creating different subject areas in a diagram, and placing shortcuts for related tables feels like I can break my entire model into subject areas and use that way. But the idea of keeping all those subject areas within one huge diagram is a shortcoming -- my own opinion. For example, I would like to print a subject area, so I can share with someone in the team. I would like to make changes only within a subject area as part of an update to the database. This kind of usability seems to be difficult to manage with a single diagram.
In any case, thanks again for your response and cheers on a good product -- I really wish it would fit our needs better.
Nevertheless, I am still not seeing how this solves our needs. My model is over 100 tables in size, and it seems like your tool forces everyone to work with a view that is always 100 tables in size.
Creating different subject areas in a diagram, and placing shortcuts for related tables feels like I can break my entire model into subject areas and use that way. But the idea of keeping all those subject areas within one huge diagram is a shortcoming -- my own opinion. For example, I would like to print a subject area, so I can share with someone in the team. I would like to make changes only within a subject area as part of an update to the database. This kind of usability seems to be difficult to manage with a single diagram.
In any case, thanks again for your response and cheers on a good product -- I really wish it would fit our needs better.