Jason,

Thanks for thoughts. I am calling new records through the "new" button from the cAdminToolbar class, which calls the new() of the form (_screen.activeform.new() I believe). It does make a call to WriteBuffer first, which could be a culprit I suppose. Need to look at that in more detail.

As far as the correct business object being the primary business object - yes, it is. I checked that a gazillion times!

The part that throws me is I've stepped through the code a dozen times - from thisform.new() through to the end. I've gone through just about every line (EXCEPT the cSelect code). It shouldn't be switching alias' anywhere I can see (and as I said, it never happens while stepping through the code).

Thanks again for the ideas. If anything else comes to mind (even a month from now!) please let me know. They can live with the band-aid till I figure this out!

Take care,

David


>David,
>How are you creating the new Contacts record? Are you calling the BizObj.New() or ThisForm.New()? If you're calling ThisForm.New(), it's going to look for the primary BizObj and call its New(). Maybe that's what you're seeing?
>
>Other than that, you may be on to something with the cSelect object. If you've forgotten to declare it, and you happen to name it loSelect, it'll be scoped as private and conflict with internal MM code. We've seen that one all too many times, and it does tend to manifest itself in the manner you're describing.