The addition of support for compound primary keys is great. It would be nice if the framework added a ReadOnly CompoundPrimaryKey Property of type PrimaryKeyValue when generating the designer file for an object. This would save having to code a custom CompoundPrimaryKey property that could be used as a Tag value for listviews, etc. It would also be nice if SeekToPrimayKey included an overload that accepted type PrimayKeyValue instead of having to pass each PrimaryKey individually.

 

-Larry

Thanks, I'll try that.

Regarding adding the column :

I called a fill method on the BO in parentformloading and saw the mykey column was now part of the currentdatatable.  The problem is that after calling the browse dialog, the currentdatatable no longer had the row.  BD creates it's own fillmethod.  How do I make sure the browse dialog either has that column or does not clobber the existing column?

Craate a view with the extra column, let the BD use that but still have the main BO get the column as I am doing with the dummy fillmethod?

On the BrowseDialog, use a custom view to populate the BO.  This should come back as part of the results.  You can also fill from it as well.  The contents of the browse dialog don't necessarily reflect what comes back if you build custom fields within the dialog.  Another option is to create the field when you come out of the browse in the data table itself.  I have done this before.  Just write a method that checks to see if the data column exists within the BO.  If not, create it.

if(!MyBO.CurrentDataTable.Columns.Contains("MyField"))
{
    DataColumn col = new("MyField", typeof(string));
    col.DefaultValue = string.Empty;
    MyBO.CurrentDataTable.Columns.Add(col);
}

On another note, you have two options on the checkbox on the date field.  Create an InfoPanel, which gives you access to the browse dialog window in which you could actually set this yourself.  The second option is for me to make a change to allow this as a new feature...which would require a new build and access to new releases.  I would go with #1 if I were you right now.

Tried using a view with the extra column for the BD, but when it does a select for the main BO it still does not create that column.

Am I really being that thick?  I want a calculated column in a BO to persist after a BD gets records.

I am going to try the approach I outline below but I would still appreciate any insight on how to get data from a BD without redefining the structure of the currentdatatable back to the SQL table defined columns

In my biggest SF app to get around this problem I grab the PKs of the BD result, create a datatable that I pass to tablevalued parameter in an SP to get my records ( posted how to do this in user contributed samples a couple years ago. )

Works great for a single key.  The problem here is that I have a compound key ... so as i am writing this, it occurs to me that since I have the mykey in my BD result I can use that single value to pass in as a TVP to an SP that will return my records - and will have the row !

Will report my results.

FWIW I solved the problem like this:

created view for BD bov_Symbology that includes the column mykey which concats the 2 char and 2 datetime columns to a 24 char string mykey

This BD fills that view with its result. 

In browse diaglog closed I grab mykey from the results into List<string> .  That goes to FillbyStringList(List<string> pklist) fill menthod of the bo_Symbology, which also has a customfield property mykey which does the same concat in its accessor

The List<string> is built into a datatable and passed to a stored procedure which has a param that accepts a previously defined Table Valued Parameter ( see my explanation of this technique in User Updates and Samples)

It returns all rows where the 4 columns concatenated make = the char(24) value of the TVP row. ( using a join is easiest)

I have a TVP in the database for int keys as well. 

This is the best way I have found to work around what I see as some major shortcoming of the BD.