I'm filling a BO using the FillDataTable method. The query that I'm using is actually hitting a view and of 9 columns I'm returning, only three have the same name as strongly typed properties in the BO.



The weirdness is that for certain column names, I get an exception:





As you can see, this is occurring when a listview is attempting to load data from the BO and attempts to get the descriptor. Now, there will be no descriptor for VendorID, because it isn't one of the properties in the BO.



What is weird, as I mentioned, is that there are several other columns (more than half) that also don't have descriptors in the BO, but they are working fine. I would understand if none of them worked, but only some of them are failing (so far, those starting with "Vendor" have failed, though I doubt that that word is causing the problem).



I'm sure I'm doing something wrong, somehow, because I'm using this sort of thing all over the place to fill listview, combos and listboxes...and it works with other columns. What could I be missing here?



Thanks!

Hmmm....that is really strange.  Like you said, this is something that you do a lot.  When loading a column in a ListView, we do not look for the strong-typed properties since you can, like you said, use a field that does not actually "belong" to the BO.

I would be curious to see this so I could run it through a debug.  You could do this on your side as well.  You could do one of two things:

1. Get your application up to the point before it fails and then turn on the exceptions through the Debug menu to break on any exception so that you can see the line it is failing on, look at the call stack and see where it is breaking.
2. Actually open up the ListView source code and place your break point in the Requery so that you can track it down.

If you could reproduce this in a sample then I would be more than happy to take a look at it also.

How would I do #2? I've never used the SF source like this. Reference the sf project?

You can do this several ways.  You can open the source, select the UI project, right-click and go into Properties.  Oonce in there, go to the debug tab and set a program to execute your application EXE in the program to execute.  Make sure that the UI project is select, and hit the play button.

Second, be sure that the SF source is built in debug.  Then be sure that your application is built in debug.  Just run your application from the EXE (not through Visual Studio).  Then open the SF source and add your break point.  Next, click Debug->Attach to Process and select your EXE process that is running.  Thhe break point should then be hit once reached.