Problems with Ttransaction Replication

The problems I have encountered with SQL 2000 transaction replication are as
follows:
1. There a lot of tables with identity columns.
2. There are about tables that don't have a primary key, thus they
can't be replicated.
3. Replication only monitors Insert, Replace and Delete commands in
the transaction logs.
I'm not too sure what the question is here - or is it just a moan ?
Transactional replication monitors data changes to a table with a primary
key. In SQL 2005 there is also the possibility of replicating most schema
changes automatically. That is the starting point. It might be that merge
replication would be more appropriate for your requirements if it is
impossible to add PKs.
HTH,
Paul Ibison