After running some tests and deleting various tables, the designer fails when it finds tables that have the same name.  For example, in my database I have a number of tables that are assigned to different schemas, but have the same name, as below:

• stat.Item
• menu.Item
• usage.Item
• etc.

When I changed the names of the tables themselves, I was able to pull up the model designer.

Mike, thank you for this. This is very interesting and could definitely be the cause of the bug. TotaalIT - does this apply to you as well?

That's it !

Same object name (I tested with views / tables and routines) in different schema's causes the wizard to close silently.

Any idea of when a fix could be released?

Sorry for the delay in getting back to you - I wanted to repro this on my end and had some trouble getting everything set up. But once I got past that - yes, this is definitely the problem. The next page of the wizard throws an exception when it tries to process the 2nd DB object that has the same name. Something about the wizard framework we use is catching that exception and making it look as though the page just closed (as if you clicked on the 'X' button in top right) which is why we don't report it to you in that dialog I mentioned. This is clearly a bug and is now being tracked (the bug reference # is 558221). Many thanks for your help in tracking it down. I wish I could, but unfortunately I can't comment on when the next official release is coming out as that hasn't been publicly announced yet.

So we have to work around the problem until the next 'official' release. Or is there any change we can get our hands on an early bugfix- or development build?

Yes, you will need to work around the problem until the next official release: We are not set up to release/support interim builds - especially given that for long periods of time we are building on top of other systems (such as the Entity Framework and various APIs/toolkits) that are not publically available.