Inheritance in Table Moduel pattern

[headware]

In his book "Patterns of Enterprise Application Architecture", Martin
Fowler says that using the Table Module pattern to model the domain
logic precludes the use of inheritance and GoF style OO design
patterns. I'm in the midst of helping to write my first 3-tiered
architecture using the Table Module pattern and am having trouble
understanding why that would be the case.

In the example he gives of the Domain Model pattern (the fully object
oriented business layer), he uses the GoF Strategy pattern to
calculate payment plans for the purchasing of different types of
software. The word processor software uses one Strategy and the
spreadsheet software uses another. Why couldn't I use that with the
Table Module pattern? Am I missing something? Table Module just uses
classes as wrapper around DataSets right? Why would that prevent you
from using inheritance and design patterns? Is this just not a good
example of the shortcomings of Table Module?

Thanks,
Dave