Comments on: The $4,000 Error Message http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/ It's the People and the Process: Pay attention to the People doing the as well as the Process. If the people don't work well together, no process will help. Thu, 20 Nov 2008 09:25:49 +0000 http://wordpress.org/?v=1.5.1-alpha by: Jiles http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-3 Fri, 20 Jul 2007 07:10:37 +0100 http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-3 Also my impression of them is all the good developers must've jumped ship once they got bought out by the black hole of software known as computer associates. The thing has been in maintenance mode ever since. Also my impression of them is all the good developers must’ve jumped ship once they got bought out by the black hole of software known as computer associates. The thing has been in maintenance mode ever since.

]]> by: Jiles Lanpe http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-2 Fri, 20 Jul 2007 07:07:45 +0100 http://tedyoung.blogsome.com/2007/04/17/the-4000-error-message/#comment-2 I feel your pain. What your client machine is missing is a crusty old database API DB-LIB. No longer supported in sql2005, you have to copy a DLL to your system directory--it can be found on either the erwin setup disk or a sql2000 client installer. The DLL’s name is “NTWDBLIB.DLL”. Nice testing process the folks at CA have. “Start up Erwin. Connect to SQL 2005. Testing done.” However yes, Erwin is truly awful. It seems riddled with bugs--switching between logical and physical models and renaming columns is a nightmare—don’t even bother using the combined model mode. And very little attention was paid to UI efficiency. How many times I need to click a bunch of buttons over and over for every single column to do some tedious task—ugh. Do anything fancy, like creating templates that create code for you...another headache that just isn't worth it. If you are proficient with the system catalogs, you're better off writing straight DDL SQL and using MSSQL's diagrams, I think. I'm curious to know if the whole market sector makes such half assed products. Is power designer this bad? Embarcadero looks pretty old and crusty, although I haven't used it much. I feel your pain. What your client machine is missing is a crusty old database API DB-LIB. No longer supported in sql2005, you have to copy a DLL to your system directory–it can be found on either the erwin setup disk or a sql2000 client installer. The DLL’s name is “NTWDBLIB.DLL”. Nice testing process the folks at CA have. “Start up Erwin. Connect to SQL 2005. Testing done.”

However yes, Erwin is truly awful. It seems riddled with bugs–switching between logical and physical models and renaming columns is a nightmare—don’t even bother using the combined model mode. And very little attention was paid to UI efficiency. How many times I need to click a bunch of buttons over and over for every single column to do some tedious task—ugh. Do anything fancy, like creating templates that create code for you…another headache that just isn’t worth it. If you are proficient with the system catalogs, you’re better off writing straight DDL SQL and using MSSQL’s diagrams, I think.

I’m curious to know if the whole market sector makes such half assed products. Is power designer this bad? Embarcadero looks pretty old and crusty, although I haven’t used it much.

]]>