>Tim:
>Just checked and the connection are the same. This is all being done on a development machine, I am using IIS also. I did do finally get some break points to work but still seems like the over ride is just being skipped over where the endpoint address etc. is defined. I must be doing something wrong but damed if I can tell where it is.
>
>Mick

Yes, but is the key name the same in your aBusinessObject as it is in the web.config file where it is trying to find it?

When you navigate to your web service are you seeing the WCFDataService Service page with the link in it?

If you are running it locally somewhere, you need to get the port for it. When I run mine locally I have a completely different address than when it is published. If you run the service you can copy the link from the page when you navigate to it.

Also just as a reference, make sure you are using the most recent hot fixed MM version. There was some things I ran into that got fixed in that version. There is another issue to look out for. My web host had three different domain pointers; www.mydomain.com, mydomain.com, and www.theirhost.mydomain.com. This does and still does cause a problem. For me I had to remove the two extra ones in order to get it to work on the hosted site.

Tim