data sources and data binding

  • Thread starter Thread starter Smola
  • Start date Start date
S

Smola

Hi all,

I have a third party system whose database I can access only through
it's specific API. I need to create a binding mechanism for a windows
forms application.

I'm not interested in writing ODBC drivers and I want to focus on
writing my own data binding objects.

What is the best approach for doing this?

After some reading I conluded that in my access-layer classes I should
implement several interfaces like IList, IBindingList etc.. This way I
can use these classes as a data source for my contols.

Am I on the right track? :)
 
Smola said:
Hi all,

I have a third party system whose database I can access only through
it's specific API. I need to create a binding mechanism for a windows
forms application.

I'm not interested in writing ODBC drivers and I want to focus on
writing my own data binding objects.

What is the best approach for doing this?

After some reading I conluded that in my access-layer classes I should
implement several interfaces like IList, IBindingList etc.. This way I
can use these classes as a data source for my contols.

Am I on the right track? :)
Click to expand...

Yes, you are correct. But you can load the class, which is an object, into
a System.Collection ArrayList, System.Collection for a strong typed
Collection, or a System.Collection.Generic List<T>, a strong typed
collection that implements IList automatically so each type of collection
can be bound to a control with an object or objects in them.




__________ Information from ESET NOD32 Antivirus, version of virus signature database 4109 (20090527) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
Smola said:
Hi all,

I have a third party system whose database I can access only through
it's specific API. I need to create a binding mechanism for a windows
forms application.

I'm not interested in writing ODBC drivers and I want to focus on
writing my own data binding objects.

What is the best approach for doing this?

After some reading I conluded that in my access-layer classes I should
implement several interfaces like IList, IBindingList etc.. This way I
can use these classes as a data source for my contols.

Am I on the right track? :)
Click to expand...

Yes, you are correct. But you can load the class, which is an object, into
a System.Collection ArrayList, System.Collection for a strong typed
Collection, or a System.Collection.Generic List<T>, a strong typed
collection that implements IList automatically so each type of collection
can be bound to a control with an object or objects in them.




__________ Information from ESET NOD32 Antivirus, version of virus signature database 4109 (20090527) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
Yes, you are correct. But you can load the class, which is an object, into
a System.Collection ArrayList, System.Collection for a strong typed
Collection, or a System.Collection.Generic List<T>, a strong typed
collection that implements IList automatically so each type of collection
can be bound to a control with an object or objects in them.
Click to expand...

I see. Thanks.
 
Yes, you are correct. But you can load the class, which is an object, into
a System.Collection ArrayList, System.Collection for a strong typed
Collection, or a System.Collection.Generic List<T>, a strong typed
collection that implements IList automatically so each type of collection
can be bound to a control with an object or objects in them.
Click to expand...

I see. Thanks.
 
Back
Top