Hi,

I've been beating my head against the dataProvider class for about a week now with no luck.  Specifically the following line:

Please correct me if I am wrong, but from my understanding the CreateObject method takes the following parameters:

1)  objectProvider - which is referenced in the web.config
2)  objectNamespace - which is the namespace where the dataProvider class resides
3)  objectAssemplyName - which is the actual name of your projects compiled dll

My dataProvider class resides in the following namespace:

In case it makes a difference, the SqlDataProvider class namespace is:

Things to check:-

• Make sure there is no default namespace and your namespace is correct, e.g. sandbox.DNN.Modules.pictureAlbum.Data
• Make sure there is no other assemblies in your bin directory it could be getting confused with. (Especially true if you rename)

Do you have the dotnetnuke project so you can step through what is happening? Is it a VB or C# Module?

Here is mine from PM:-

My assembly is called "DnnForge.PrivateMessages.SqlDataProvider" and my namespace is DnnForge.PrivateMessages.SqlDataProvider"

I think the CreateObject adds the defaultProvider to the call..

Have you looked at the hello world tutorial on DnnJungle? I think your data provider isn't being loaded correctly..

You can find the tutorial here..

Smcculloch,  Thanks for all of your help, I've determined what the problem is and everything is working fine now.

Basically, everything above is correct except for one thing.  The namespace for the sqlDataProvider class is:

Namespace sandbox.DNN.Modules.pictureAlbum.SQLDataProvider.Data

When it should be in the same namespace as the abstract dataProvider class in the module project which is:

Namespace sandbox.DNN.Modules.pictureAlbum.Data.

So, for anyone else reading this post in the future, if you are having similar problems check the following:

1)  Make sure that both the sqlDataProvider class and the DataProvider class are in the same namespace.
2)  Verify those namespaces using the object browser in visual studio
3)  Verify that the solution outputs the dlls for both the module and data provider projects to the dotNetNuke bin directory
4)  the CreateObject call in the dataProvider class should be as follows:

CreateObject("data", "<NAMESPACE OF DATAPROVIDERS>", "<NAME OF MODULE DLL>", DataProvider)

Where the following explainations apply:

<NAMESPACE OF DATAPROVIDERS> = The namespace of the dataprovider class in the module project and the namespace of the sqldataprovider class in the dataProvider project (they should be in the same namespace).

<NAME OF MODULE DLL> = This is the name of the module dll that should be compiled into the dotNetNuke bin directory when the project is built (minus the ".dll" extension).

I hope that this helps any readers in the future avoid any of the heartache I've been through trying to figure this out.

I've set this post to email me if any replies are posted, please feel free to contact me if you are experiencing similar problems and the latter steps do not resolve the issue.