Hi Gary,

So... one follow up:

>it doesn't matter how I set lAutoPk because it respects the seniority of AfterNew (in my case).

I didn't realize this. So, no matter what lAutoPk is set to, the AfterNew() code over-rules that - with the type of code I was using? And, you do something somewhat similar to what I was doing (with the suggestion you made of not using the regular fox replace)?

Gary... I am updating this message after doing a little more study.
I notice in the current CodeMine sample cde AfterNew(), Dave still used the replace like I was. He probably just hasn't updated that yet.

Would you mind showing me how the code would look for this:

REPLACE FundTmpID WITH PRIMARYKEY('Fundstmp','FundTmpID','Counters.Primary Key Batch Money')

without using the native VFP replace?

Would it be:

* This is creating the PrimaryKey for the child view.
=PRIMARYKEY('Fundstmp','FundTmpID','Counters.Primary Key Batch Money')

Then, the following is placing the Parent key in the child view for the relation. However, wouldn't CodeMine have already done this... since the lPkAuto is set True in the CDE?

THIS.Replace('Fundstmp','PeopleID',Person.PeopleID)

Again, thanks for the help - and the additional clarification.

Mel Cummings