Jim,

That's what the Visio tool was expecting, to find the same key field name in both tables (a rather artificial constraint on Visio's part). On the whole though I'm happy with iID in all tables it makes some code easier. But I'm not too zealous on the issue. *s*

>I use iTableCodeID for both the PK and the FK just cause it makes sense that if they are related, have the same domain, hold the same values, then they should have the same names.