When you say DataSource, what DataSource are you referring to? There are many, including the SqlDataSource, XmlDataSource and the ObjectDataSource that you mentioned.
It all depends what you want to accomplish. If you have straight forward database data, a SqlDataSource is fine. Like you said, it breaks good three-tier design, but for many sites this isn't a problem. However, you should realize it's not that easy to move existing code from a SqlDataSource to an ObjectDataSource, so, if time and knowledge permits, you may want to start using an ObjectDataSource right away.
Personally, I use SqlDataSource controls for quick and dirty applications (prototypes, demos) and for simple data binding scenarios like drop down lists. But, you'll find they work in more complicated CRUD scenarios (Create, Read, Update and Delete) as well.
quote:I am planning to run few chapters with DatasOurceControl initaially
Not sure what you mean with this...
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results
and Beginning Dreamweaver MX / MX 2004