Custom Modules

Re: When creating a new module no sqldataprovider created

adefwebserver — Tue, 25 Jul 2006 03:56:31 GMT

ok no problem :)

Re: When creating a new module no sqldataprovider created

Taisho — Mon, 24 Jul 2006 17:39:50 GMT

Wow that's kinda harsh. Especially considering that the Starter Kit was changed and it no longer creates the SQL Module settings file. That is why it's not there anymore.

The solution is to instead use the .dnn file that is created and use that instead.

Thanks...this answers my quesiton.
However, my response about thinking you were responding to the wrong post above was not an insult, nor was it harsh...I literally thought you meant to respond to a different post. I figured someone else had asked a question, and you meant to respond to that person but put it in this thread instead by mistake.

I could have worded it better, I suppose, though. IE: I could have said "Did you mean to respond to someone elses post?". Thereore I aplogize for the overbearing tone of my message, and the complete uselessness of my following message.

Re: When creating a new module no sqldataprovider created

adefwebserver — Fri, 21 Jul 2006 13:28:51 GMT

Taisho:
Does anyone have a reply remotely connected with my question?

Actually I do... nevermind :)

Re: When creating a new module no sqldataprovider created

adefwebserver — Fri, 21 Jul 2006 13:24:47 GMT

Taisho:
Your replying to the wrong post. Please remove.

Wow that's kinda harsh. Especially considering that the Starter Kit was changed and it no longer creates the SQL Module settings file. That is why it's not there anymore.

The solution is to instead use the .dnn file that is created and use that instead.

Now, if I am still wrong then please indicate why.

Re: When creating a new module no sqldataprovider created

ecktwo — Thu, 20 Jul 2006 18:32:40 GMT

Taisho:
Your replying to the wrong post. Please remove.

No need to dismiss adefwebserver's post so quickly. Take the tutorial offered at his website to solve your problem. (notice the DAL and DAL+? That's what your question is referring to.)

Re: When creating a new module no sqldataprovider created

Taisho — Thu, 20 Jul 2006 17:49:44 GMT

Some more details if it helps:
01.00.00.sqldataprovider is there, but TestMod.sqldataprovider is not.
Book says run sql script for TestMod.sqldataprovider, then run script for 01.00.00.sqldataprovider.
The script for 01.00.00.sqldataprovider runs; however, the script for TestMod.sqldataprovider cannot be run, because it does not exist.

System notes: OS = Windows 2003 Server with Sp1. Hardware = Dell 3100 Pentium 4 with 2 gigabytes of memory. The system is part of a domain, but not a domain controller.

Re: When creating a new module no sqldataprovider created

Taisho — Thu, 20 Jul 2006 14:43:39 GMT

Does anyone have a reply remotely connected with my question?

Re: When creating a new module no sqldataprovider created

Taisho — Thu, 20 Jul 2006 14:18:57 GMT

Your replying to the wrong post. Please remove.

Re: When creating a new module no sqldataprovider created

adefwebserver — Thu, 20 Jul 2006 02:08:23 GMT

From the HOST menu select "Module Definitions"
Click the small down arrow in the upper left hand corner of the Module Definitions menu and select "Add New Module"
Select "GuestBook.dnn" in the Module Manifest drop-down and click Install

When creating a new module no sqldataprovider created

Taisho — Wed, 19 Jul 2006 21:24:14 GMT

I did the following:
website --> add new item -->dotnetnuke module
renamed .modulename to ... someModule, for example.
Clicked add.

Most of the "stuff" that I will need (according to the book I have) is then added, and I rename the module to someModule in AppCode and DeskTopModules, as per the instructions on the help page that pops up.

However, in the DeskTopModules inside the new someModule directory, there is no someModule.sqldataprovider.

What have I missed in creating this new module, that this required item is not being created?