Can't solve replication conflict

[Peter Kinross]

My main Db is replicated on 2 other computers. A couple of weeks ago, I had problem editing a record and had to rebuild one of the 80 or so tables. Now when I open the Design Master I get a conflict error, yet the Replication Conflict Viewer shows ‘<No conflict tables>’.
Anyone have any idea on how I can resolve the conflict?

[HansV]

See Microsoft Replication Conflict Viewer displays “<No conflict tables>” even when synchronization conflicts exist among the replicas in Microsoft Access.

(The real solution would be to stop using replication, but that would cause other problems of course)

[Peter Kinross]

Unfortunately one of the computers is a laptop, so replication is the only solution.
I solved the problem. I manually resolved any conflicts, deleting each conflict table as I went - which worked - sort of. But one replication table was left, 'MSysRepInfo_Conflict'. And that table can't be touched. Neither rows deleted nor the table itself deleted. While that was still around, although there were now no conflicts, the problem persisted.
So I un-replicated the Design Master using Pacific Database's Unreplicate. Pretty painless. Then I made it replicable, and created 2 replicas. Now it all works just fine again (until next replication error).
So, thanks for the input.