>I'm going to say this again....
>
>One of the issues I have with your questions here is that you often don't do what's suggested and go off on your own, doing things that circle back to earlier suggestions.
>
>So, again to repeat what Viv and I have both said...
>
>Check what is being sent over the wire. If the json isn't being created, you'll get nulls sent to the controller.
>
>
This is the strange thing - this is what is being sent

Client.Address aa
Client.Contact1.Contact
Client.Contact1.Email
Client.Contact1.phoneInfo...
Client.Contact1.phoneInfo...
Client.Contact2.Contact
Client.Contact2.Email
Client.Contact2.phoneInfo... searchClientNo=
Client.Contact2.phoneInfo...
ClientId 240
ClientName Ab Spare
ClientNumber 1002
fntype Edit
searchClientName a

----------------------------

fntype=Edit&ClientId=240&ClientNumber=1002&ClientName=Ab+Spare&Client.Address=aa&Client.Contact1.Contact=&Client.Contact1.Email=&Client.Contact1.phoneInfo.Phone=&Client.Contact1.phoneInfo.Ext=&Client.Contact2.Contact=&Client.Contact2.Email=&Client.Contact2.phoneInfo.Phone=&Client.Contact2.phoneInfo.Ext=searchClientNo=&searchClientName=a

--------------------------------
So, I am thinking the problem is in Concatenation I've been trying - I probably should not use concat and I just commented this out:

Here is what I have:

 var form = $('form', this);
            debugger;
            var oForm = form.serialize();
            //oForm = oForm.concat($('#frmClientsSearch').serialize());

So, right now I commented out the concat part - I wanted to pass both the model and the calling form data also.