Hi Sakis,

First, sorry for the BIG BOLD RED, it's not my choise but a strange results from my cut and paste!

Normaly, you do not have to rebuild the module. I never used the Oracle Data Provider, Sanjay must know if you have to rebuild.

I do not know about scalability of SQL Server 2005 Expres because I do not use it. Try to post in the forum "Chat About-it!".

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.

Sakis - I've started the conversion already and am hoping to have a working copy by late next week (if that works for you). You would probably be the first person to use it - if that's ok with you.

If you do create the oracledataprovider yourself, you can do that too but yes it would still require the core oracle dataprovider (unless you've already written that too)...

Gilles - the product (AcuitiDP) works the same way as the SQL Server version - ie it comes with a different web.config file which points to all the oracle implementations of the various core (and module) stored proc calls.  Since DNN is abstracted at the data access layer, it's is possible to target a different database platform without making any changes in the core code (or module code) itself. Most of the core modules work out of the box without doing a recompile but there are a couple that I've had to recompile to get them to work against the oracle version. 
I'll try and put together a brief description of how the provider works - I'd kinda assumed that most people would already be familiar with that since it's basically building upon the existing architecture of DotnetNuke itself :)...

Sanjay

 

---

Gilles - that would be perfect - if you could send the next version whenever you're ready. Typically I try to release the oracle version of a core module as soon as I can determine that it's stable enough and that people would not have issues with it. 
I have had to rebuild the following core modules
a) HTML/Text - reason for this is because the core version does not use the WAP Model for this module and I couldn't find a suitable way to inherit the dataprovider class to be able to create the corresponding overrides for Oracle.
b) Survey Module - same reason as above.
c) XML Module - there was an issue with one of the calls which was failing in Oracle and I had to modify how it was called from within the XML module class.
d) Reports Module - this one is still proving a nightmare and I've started the conversion process but have so far being unable to complete it - one of the issues with this module is that it uses the SqlDataReader instead of IDataReader and since that's a big no-no for Oracle, I've had to recompile it. However I've run into other issues with this module too (use of ExecuteNonQuery, etc) which have thus far proved to be cumbersome to convert over.

Sanjay

---