Hi Joe
Well I try to explain it in more detail.
I have a full flash site (the site has nothing to do with DNN). On this site there will be several pages i.e.
about us
services
solutions
clients
contacs
documents
In the section ' documents ' there will be a short description of the type of documents that are available online + there will be a button named "access database" (everything still made using flash)
When a visitor chooses to access the database, after clicking on the button, it should transfer him to the login page of the "DNN site". The whole "DNN site" will consist of different types of modules, and pages that are dedicated to the document section. To access the "DNN environment" a user needs to login or to register ... so from this point now on we can say that the user is using only DNN. (of course on this site, there will be a link for the navigation back to the flash site).
When I was thinking about the solution (because of the setup that is needed for DNN ~ IIS server, web.config file as you mentioned atc.) - one solution could be following ?
let's say I have registered the domain : company.com (so my website will be www.company.com ~ 4 us newbies ...)
On this domain there's going to be the "flash environment".
When the visitor chooses to access the database (he's still in the flash environment) - the button in the ' document section ' metioned above, will be linked with a domain : documents.company.com (i.e. a subdomain ~ the related site will be www.documents.company.com)
On this subdomain there will be the whole DNN environment installed.
Is this the right solution of the problem ? Do you have any suggestions ?
I appreciate any suggestions that could lead to a simple, elegant solution