I'm just starting a web app in 1.65 and was doing some 'fooling around'.  Inserted a listview into a page, and after setting the population settings using a registered BO, received a design time error message that "an unhandled exception has occurred.  MicroFour.StrataFrame.UI.Web.WebListViewPopulationColumnCollection must have items of type MicroFour.StrataFrame.UI.Web.WebListViewPopulationColumn."  There was more, but in essense it was saying that instead of getting the type it was expecting, it was getting a populationcolumn of type System.Web.UI.HtmlControls.HtmlGenericControl.

The project built successfully, but yield the following error at runtime:

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: MicroFour.StrataFrame.UI.Web.WebListViewPopulationColumnCollection must have items of type 'MicroFour.StrataFrame.UI.Web.WebListViewPopulationColumn'. 'microfour.strataframe.ui.web.weblistviewpopulationcolumn' is of type 'System.Web.UI.HtmlControls.HtmlGenericControl'.

Source Error:

Line 33isplayFieldNames="cSiteName|" MethodToExecute="FillAll;">

Line 34:<FormatColumns>

Line 35:<microfour.strataframe.ui.web.weblistviewpopulationcolumn columnalignment="Left" 

Line 36:columnheader="Site Name" columnwidth="120pc" formatstring="{0}" 

Line 37: headeralignment="Left" populationtype="FormattedString"></microfour.strataframe.ui.web.weblistviewpopulationcolumn>

Your suggestions are on the mark and I'm up and running.  One note -- the pipe after the field name is still being generated by the PopulationDataSourceSettings designer, but it doesnt' appear to impede anything.  So it's not the culprit ....

I did see where my earlier web.config had the PrefixTag entries in it and the new one didn't.  So that was definitely the problem.

The devExpress ASPxGridView generates an error ("Error Rendering Control"), but the ASPxDataView seems to work ok thus far.  I understand this is something you have addressed yet -- just thought you might like to know ....

Thanks again for your help!

Gratefully,

m

FYI, on further testing, it looks like the problem with the devExpress ASPxGridView (and the standard GridView, for that matter) is with GUIDs.  Also, the standard Gridview indicates that the WebBusinessBindingSource does not support paging.  Is this correct?

Mark

Correct.  If you want paging, do this through the BO by creating a Fill method that pages through the records.  For example, you could create a Fill method called FillNext100 and have it take into account the primary key or whichever root value you want to use.  This is how we use paging...having this automated is probably not going to happen any time soon as this will require a significant implementation to support all of these different controls.  But you can do it manually right now.