Michael,

>I think this is going to be another one of those things where I will show my feet of clay but here goes.
>
>I have a test app I have been using to test out some new ideas, actually the MM .NET Jump Start. I created a WPF project and was able to create a quite respectable Customer maintenance screen with aero effect, using the new 3.51 data gid. Well anyway the project that I hope to roll some of this into really needs to use WCF. So I followed the example in the manual for Remote Data Access with WCF, and it seems like I'm not using WCF at all. I used the method of just adding into the app.config a key for DefaultDataAccessMode, when I set it to Local it works normally, when I set it to WCF it errors out that "The ConnectionString property has not been initialized.". If I also do like the documentation says and put a break point in the mmDataAccessWCFSql.cs file it doesn't get there.
>
>Am I barking up the wrong tree are the hooks for WCF not in the WPF project templates or something? When I put a break on the Factor.cs "override mmDataAccessSql CreateDataAccessSql()" the program doesn't break for it?
>
>Mick

When you are running in Local Mode are you using SQLDataAccessClass? Do you have the service running locally on your machine or on another machine? For WCF mode, the connection string is in the web.config file of the service and the DatabaseKey has to match from your business objects over to the service in order to find that connection string.

I have a current application running with WCF and I certainly had some pains along the way. The setup is really quite simple once you figure it out however. OakLeaf did a great job on this project but I am hoping for a better way to extend it beyond just data Access.
If I can help with this, let me know.
Tim