I am looking to bind it with DW.NET (from Sybase). It doesn't currently support Object Source. However it does support DataTable. I am looking to persist manually from DW on event triggers like RowChangedEvent, InsertRow , DeleteRow, columnChanged, sort, group, filter, retrieve(fill), update(update) events with llblgen object source. I am looking for the generic code including that will preserve the state of the column & rows that dw.net provides to be persisted with llblgensource.

Any suggestions of how to manually integrate the llblgen source with datawindow control. does llblgen collections or datasource has these kind of events that i could map it so the code can be generically written. how does sorting, grouping, rowfocuschanged event, rowfocuschangingevent in a datagridview correlate with llblgen object source.

I have other control tools like Infragistics to look into. But, this could save us a lot of time & money if we could reuse these some 1000's of datawindow controls already existing. any help I am having the latest llblgen pro, dw.net 2.5. thanks vsv

Hi vsv,

I don't know if this is an easy way but you can start checking out the source code (_LLBLGenProDataSource2_ and _LLBLGenProDataSourceBase _classes) at LLBLGenProDataSourceClasses.cs and see how LLBLGenDataSource implement the databinding.

DW.NET is winforms? Have you tried binding an entity or entity collection to it? If it supports datatable, it could support entitycollection as well.

Unfortunately, it doesn't support it.

Is it possible to get the source code during the trial period. thanks

vsv wrote:

Is it possible to get the source code during the trial period. thanks

No.

The code implements all databinding interfaces (IListSource, ITypedList, IBindingList, INotifyPropertyChanged etc.) and if the dw.net component doesn't understand these, you can't use entities with that component.

Are the entities & collections available as DataSet. If yes, how to transform it back & forth. thanks

You can project the entity query onto a datatable (see Using the generated code -> Adapter -> Fetching DataReaders and projections), but it's not ideal because you can't use prefetch paths etc. So instead of going through all this trouble, I'd either opt for a total dataset oriented solution or drop dw.net.