No worries...I am just glad you got it going

Sorry for wasting your time!!  I thought I had installed the new db structures the 1st time I installed the beta but obviously I didn't. 

Thanks!!

That makes it simple   You didn't update your StrataFrame database structures.  There are new columns that have been added, so you need to be sure that the StrataFrame database is updated during the installation.  These are two new columns that have been added to the DBEPreferences table...they are missing.  So run the setup again and BE SURE to let the structures update.

Thanks Trent!!  Attached is a copy of the error and stack trace that is being generated.

I rebuilt the installation with the changes so you can see what error you are getting.  You can get it here: http://forum.strataframe.net/FindPost14525.aspx .

What do I do in the meantime?  I need to get this working.

I've added a try/catch to the method that populates the lists within the type editor dialog.  It will force the wait window to go away and it will also show the red exception dialog when you receive an error while it's loading the dialog.  Hopefully that will give us some more insight into what's causing the issue.  It will be part of 1.6.5 when it's released.

I created a new project, added a new BO connected to a different database, added a combobox to the form, bound the combobox to the new BO then tried to set the PopulationDataSourceSettings and I get the same problem.  So it appears that the problem is NOT with the BOs in my original project but may have something to do with SF itself. 

For what it's worth, all the PopulationDataSourceSettings in my solution were originally set when I was using SF 1.6.1.  This is the 1st time I'm trying to set them using 1.6.5.

Yes, if a create a new form and drop a combobox on it the problem persists.  But here's what I can do.  If I go into the form.designer.vb code I can add a ListPopulationSettings object, set the proper properties on it then set the comboxes PopulationDataSourcesSettings to the ListPopulationSettings object.  Probably a dangerous thing to do but I have it semi-working as a work-around for now.

Actaully if that method cannot be found it will not produce an error...we take that into account.  I think that the error is coming from enumerating through the BOs.  If you drop on a new combo on a test form, does the issue persist?