Just viewing the dnnC video tut about setting up on a web host server.
And it looks like it's pretty much recommended to stick with version 1, because of compatability with modules.

Also my webhost is giving me 1 MS SQL database and 1 My SQL database to start, but I get unlimited Access databases mdb's then. I read somewhere that I could possibly use Access databases. I think it might be a good idea for me to setup a sample DNNuker using my access databases.
Any thoughts on this, I've not alot of experience with ACCESS mdb's either , I just know I wouldn't be using up my one MS SQL.
Stumped...?!?


I've no idea what modules I may want, or really what sort of website I'm going to create. I have two focuses, one being a sports club type of website for disc golf, and the other being a developer community site promoting the latest internet technologies, like DNN even.
Can I possibly combine two totally different websites into one DNN, I'm sure the skinning wouldn't be a problem, it's just the logic of the layout.
Thanks for any ideas on where to begin then
Nice selection of smilies !

Is there any way to edit earlier posts, I'm known to be obsessed with correcting something I entered earlier
Anyways looking at version 3.2 doc's I get this(below) regarding ACCESS mdb's, looks like it would be a huge sacrifice to only run on an access database. Am I right?
------------------------------------------------
MS Access has its own proprietary SQL language called JET SQL. In contrast to Transact-SQL, JET SQL is an extremely limited scripting language as it has no support for local variables, conditional branches, or looping. This limits the queries to very simple CRUD operations. A few syntactical items to note are JET does not accept script formatting using tabs, stored queries need () around the parameter list and parameter names must be wrapped in [@], NULL must be handled using the isnull() function, the word “outer” is dropped from the join clause, the Now() function returns the current date, bit fields use boolean True and False specification, and the query must be completed with a semi-colon (“;”).

Hello,

Install DNN using SQL server, don't bother with Access it's too limited and to be honest I didn't think access was still compatible with DNN, I thought it was just available with DNN2.1.2.

Which version of DNN to install is a more complicated question and one that always pops up. - DNN4 is still regarded as work in progress which is why I haven't switched to DNN4 yet, there are still problems that occur on DNN4 (although the latest release DNN4.0.3 is supposed to have fixed a lot of the bugs), whereas DNN3 is more stable and reliable. - So for a live production site I will always opt for DNN3.

The question is will you be coding any of your own modules, will you want to code in ASP.NET2.0 or ASP.NET1.1 - If you want to use the latest ASP.NET2.0 then you will need to install DNN4.

DotNetNuke is a portal, so you can create several portals using one DotNetNuke Installation with one SQL server database and each portal can have it's own domain name.

- What you need to check with your hosting provider is how much extra they charge for additional domain names, I've quite often found that you might as well purchase hosting for a separate website.

Thanks,