Erik Porter is reviewing the ADO.NET for a book he is writing. He questions why HasChanges is a method and not a property. Erik implies that methods change states of an object in a complex way, but properties only change it a little.
In a comment, Paul Laudeman thinks the decision rides on the complexity of the code.
I like how Microsoft describes properties vs. methods in the MSDN library.