In this tutorial
http://www.asp.net/learn/dataaccess/....aspx?tabid=63

it says:

">>>> The ItemTemplate can be created by hand (through the declarative syntax) or can be auto-created by binding the FormView to a data source control through the Designer. This auto-created ItemTemplate contains HTML that lists the name of each field and a Label control whose Text property is bound to the field's value. This approach also auto-creates an InsertItemTemplate and EditItemTemplate, both of which are populated with input controls for each of the data fields returned by the data source control.
If you want to auto-create the template, from the FormView's smart tag add a new ObjectDataSource control that invokes the ProductsBLL class's GetProducts() method. This will create a FormView with an ItemTemplate, InsertItemTemplate, and EditItemTemplate. <<<"

I a learning test, I can't get this to autogenerate my FormView templates.

I start with a new form. Add a new FormView. Use the designer in the FormView to select "new data source". Select "Object" as type of datasource. Specify the object datasource.....whirrrrr....no autoformatted templates show up.

I'm using an objectdatasource that just has a select method...it builds a datatable from scratch in memory and returns it. I've used this specific objectdatasource object and method for several other learning tests and it has worked fine so far.

Any suggestions on how to get this autogeneration of FormView templates to work in my test case would be appreciated.

Thanks!

use a gridview

Live in fragments no longer. Only connect.

Thanks for post. Formview is chosen so to only see one record at a time. Gridview does not appear to offer autogenerate of template fields, either.

After further research, and no other mention of this capability, I'm concluding that the author of the cited article was incorrect in asserting that FormView had a template autogenerate feature.

It seems to want a strongly typed data table in order to autogenerate the formview templates. It doesn't care whether the strongly typed table comes from a tableadapter or a custom class.

RE-solved!