Gail, thanks for the reply. I had forgotten about the pseudo-simple mode and I'll bet that is what is going on - I can't think of any other way that this transaction log isn't blowing up. I will set that Subscriber database back to Simple Recovery Mode so I can start breathing again.

To summarize then - the transaction log on the Subscriber database does get written to and does grow when there are inserts to that database because of activity arriving from the publisher/distributor. If my Subscriber database had been in honest-to-goodness Full Recovery Mode, I would have heard about it pretty quick, just like any other Full Recovery Mode situation where the transaction log is not being backed up. But because I wasn't in Full Recovery Mode, the log file was being truncated by the ongoing Checkpoints. Is that an accurate summary?

Thanks again.

Willem