After the update I am no longer able to run the business object mapper on an existing project.  When I created a new project I could run the business object mapper but clicking on the config link causes the mapper to close.  Any suggestions.

Oh, when you installed the updated, did you choose to install the database, or did you bypass that step?



I forgot to list in on the Update Blog that you have to install the database (nothing that's there will be deleted) so that the structure can be udpated. The structure for some of the tables had to be updated to support the Oracle and OLE DB connections for the Business Object Mapper.



If you didn't choose to install the database udpate, you'll need to re-install the update and choose to deploy it.



Sorry, Scott, I'm updating the Update Blog right now

That solved the problem.  Thanks

Excellent. Sorry I didn't post that the first time.

Normally when you get an exception at runtime, you'll get a nice, pretty, big, red window that details the exception, inner excpetions and stack traces. However, with all design-time extensibility coding within Visual Studio, you can forget your structured exception handling as VS likes to snuff all of the exeptions. Hence, when your BOM window just "disappears" it threw an exception and VS killed it.

That's useful info. I will try it.



How about the fact that when you actually get it open, and select project configuration or modify project configuration, the save button does nothing?

When you installed the new update, did you let the databases update as well?  We changed some data structures to the StrataFrame database which will cause an exception (and thus no report since within the VS IDE).  If not, go back and reinstall the update and let the databases update.  See if the BO Mapper comes up after the install.  This is the most common issue when the BO Mapper will not appear.

Daniel,



The problem you were receiving was because your database was not updated properly... When you attempt to open the business object mapper's project configuration dialog, the fields would not exist, an exception would be thrown, and the form would disappear.



The current update (posted about 30 mins ago) fixes the problem... the install did not properly migrate the database forward for SQL Server 2000. This is why Larry was working after he removed his database and re-created it from scratch.