Hello Greg

Yes DNN can do this, by creating Parent or Child Portals (sites).

Lee has a tutorial on this feature (issue 17 see link below) you might find this of interest.

http://www.dnncreative.com/Issueno1...fault.aspx


Regards
Lynn

For that matter, you can make them all parents. Think of DNN the host and that this host can contian many portals. What would matter is what data you want to share. If you want to share user databases, store databases etc, you would want to go parent child, with all of the shared modules being set up on the parent. If sharing information (which appears to be somewhat dicey to begin with) isnt important, then you can make them all parent. I work with doctors offices and my guesss is they will want their patients information on thier site only, so parent sites would be fine.

Oh yeah the reason I went through this. I have found that in the DNN parent child relationship, if DNn encounters a hiccup, instead of returning to the child home page , you are returned to the home page of the parent. This could be a real probelm in your case and annoying in any case.

Slightly different question ...

I want to create a website with two portals (port a and port b). Can I share content between them. Such as in Port A, can I install the FAQ module and say to use the content from Port B FAQ ?

Thanks

Unfortunately DotNetNuke is not currently set up to share information between portals. The only method you can use is to set up RSS feeds.

For instance on portal a with module 1 you will set it up to generate an RSS feed of its data.
On portal b using the news feeds module you can display the RSS feed of module 1 in portal a