No, you misunderstood me. OJB can handle multi-column primarykeys without problems. The issue here is that the value of the primarykey of this relationship object is given by the primarykey values of the two related objects. So neither OJB nor the Database can fill the primarykey value in automatically, you have to do it manually before inserting the object into the database. My objection was simply to abuse the primarykey concept for this, but if it works for you, just go ahead.
Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
