>
>Well, sure, in your Many file the Name would be a regular index, but in your Manager file, the manager name could be a candidate key...
>
>I just tried this.. I set up a Manager table with id as primary and name as candidate. (of course, this doesn't allow two managers with the same name, but, if you did have that, this wouldn't work even if you have keed it.)
>
>Then, I set up a Department file with manager field with a regular index on manager. I related the two files and set RI to cascade key changes to the child file. I entered a few records and it worked great.
>
>BOb


I *do* appreciate your replies, but you fixed the wrong problem <g>. I did not bring the Manager table into it, that's handled nicely already.

My problem is how to refresh the Manager in the *Projects* table from the entry in the Departments table (linked on Department Id).

Refreshing the Manager in the Departments table from the Manager table works just fine as you've described.

I've been thinking about adding code to the PostSaveHook method (in Departments bizobj) to update the entries in the Projects table whenever the Manager field changes in the Department table. But with all the environmental considerations of MM, I'm not quite sure how to proceed without gumming up the works.

Once again, I thank you for your imput.

...John