Second, you can't just set the userID like I did, you have to pass the full bean of the first table to the second table.
Be careful, you don't *need* to set it to maintain integrity outside of the transaction boundary, but if both of them are in fact state on the object I *would* be sure to set them at the same time so that the object state is consistent within the transaction boundaries. Particularly in the case of container managed transactions (this isn't necessarily EJb containers, I do it in web containers) where something else may be using the same object within the same transaction.
I am glad it was solved!
-Brian
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
