I write code and I write code accessing erwin Data Modeler's API, the Application Programming Interface, so that I can use Excel to update erwin Data Modeler and then get those updates and put them back into spreadsheets. The only thing I wish is that their API documentation was a little bit clearer and that it had better examples of successful code. To me, examples are worth a hundred pages of reference documentation. Just give me an example of how you use it, and that really helps. I know that's a nitpicking thing, but I wish their API documentation had a lot more examples of code that actually worked to do the things that they're talking about. As far as erwin Data Modeler itself goes, when we have a lot of tables, I have some erwin Data Modeler files that have thousands of tables in them, up to 3,000 or 4,000 tables. When erwin Data Modeler files start getting that big, it takes a really long time, I'd say a minute or more, to open the file. Whenever I'm working in it, sometimes there are operations that also take a long time, so as erwin Data Modeler files get larger, the response time really slows down. An irritation is that every now and then, when I'm working and usually when I have multiple erwin Data Modeler files open at the same time, I get a glitch where a lot of the text fields get solid black, the first eight characters of column names might be blacked out with a rectangle. All I have to do is close erwin Data Modeler, shut it down, and bring it back up, and then everything is fine. It doesn't happen all the time, only occasionally, maybe once or twice a week, and those are the only two things I can say. The previous version of erwin Data Modeler used to crash unaccountably, but this one hasn't ever crashed on me, so it's been a lot more stable than the previous version that we had.
