I was using the Standard maintenance form, i followed the tutorial from the help file. I dont see a tutorial in vb that conforms to the step by step in the help manual so i cant test it against my example. I will start again and see if i can reproduce it.

PS: The Full sample provided in vb called "StrataFrameSample.sln" Click Customer Maintenenance then "Browse" then "Search" and double click on a returned record. Produces error

System.InvalidCastException was unhandled by user code
  Message="Specified cast is not valid."
  Source="StrataFrameSample"
  StackTrace:
       at StrataFrameSample.CustomersBO.get_cust_phonedaytype() in C:\Program Files\MicroFour\StrataFrame\VB.NET Samples\WinForms Sample\StrataFrameSample\Business Objects\CustomersBO.Designer.vb:line 548
       at StrataFrameSample.CustomersBO.Field_cust_phonedaytype_Descriptor.GetValue(Object component) in C:\Program Files\MicroFour\StrataFrame\VB.NET Samples\WinForms Sample\StrataFrameSample\Business Objects\CustomersBO.Designer.vb:line 1291
       at System.Windows.Forms.BindToObject.GetValue()
       at System.Windows.Forms.Binding.PushData(Boolean force)

Regards Wayne

As for the problem of the controls not refreshing when the business object is navigated, if you can reproduce it, let me know, and ZIP your solution and post it here on the forum.

I having a similar problem; getting an InvalidCastException using version 1.41. I have a standard SF maint. form. On the form I have two controls, a textbox and combo box. The combo box is populated by an enumeration and is bound to the BO. The text box is bound to a string property on the BO. If I open the maintenance form and click on “New” I can add a new record with no error. However if I click on browse, retrieve some records and then click “New” I get the InvalidCastException. If I unbind the combo box from the BO everything works fine.

-Larry

When you use an enumeration to populate a combobox, the SelectedValue (which is what the combobox will bind to by default) actually contains enumeration values, not integer values.  So, to bind to that combobox, you'll need to go to the BOMapper and customize the field to return the enumeration value rather than an integer. 

If you don't want to customize the field, you'll have to populate the combo manually, or it will continue to throw the InvalidCastException

-Larry

1) MyBO's SQL table has a field called "field1"

2) You customize "field1" to, say, trim the value.

3) You change the structure of the SQL table so that "field1" no longer exists (or was renamed).

4) The BOMapper thinks the field disappeared, but the customization record still exists within the BOMapper.

So, the warning is just telling you that not all of the fields that you customized are being created on the business object.

As for your other error, can you post the red error message that contains the stack trace... might tell us where that exception is being thrown from

Ben,

Thanks for the explanation of the warning message. I’ve attached a couple of screen shots. The two field sample I’m using is a stripped down sample of a more complex object. While that form includes an enum bound combo box it was a string property that was getting the same error.  In stepping through the code I noticed that when “New” was clicked without first doing a browse, any fields that were not set to allow null in OM were automatically set to default non-NULL values. When a Browse was done and rows retrieved prior to clicking on “New’ the fields in the BO were not automatically set to defaults.

-Larry

Correct me if I'm wrong but I was under the impression that the OM alternate values for null was to eliminate problems where NULL data was returned from the database. In this case I'm adding a new row. Since I don't have the source for 1.41 I'm not able to step through all of the code but what I've noticed is that in the cases where I'm receiving the errors is that fileds that would automatically be set to a non null value (even if they were not configured to do so in OM) for a new row are not being set.

-Larry

On both my test BO and the actual application I'm coding the AllowNullValueOnNewRow on the BO is set to False. If it helps, when receiving this error the BO's set-default-values code never gets executed. It fails right after retrieving the BO's FieldDbTypes.

-Larry

Whatever is causing the problem appears to have been introduced in v1.41. I moved the code back to version 1.4 and everything works as expected.

-Larry

When you get the exception in your program, and the .NET unhandled exception dialog pops up, press "Continue" on your debug and you should get the red "Application Error" window that will have a complete list of the exceptions and inner exceptions and the stack traces of all of the exceptions concatenated together.  That should give me a clue where it's coming from.  You can copy/paste the content of that window and post it here.

It took me a few minutes to get back to you since I had to re-install v1.41.

Continuing just brings up the same error for the next field and so on. Once I've cycled through all the fields the maint form is displayed and I'm able to enter the data and save the record.

-Larry

A red error window is never displayed. Attached is a screen shot with the stack trace associated with the error.

-Larry

Any estimate of when a fix will be available? If it's going to be awhile I'll go back to v1.4

-Larry

That fixed the problem  Thanks for the quick response.

-Larry