I would suggest that you have a closer look at the way DNN works before trying to force it to do things in ways it was not designed for.

Ultimately, all pages in a DNN site are hosted from a single file - being default.aspx.  The exact content, including the selection of which tab to render and which modules to display are controlled at runtime by the contents of the sites database and the various parameters passed from page request to page request.

So lets assume then that you have a module on a page somewhere in your site, that contains your module to display the datalist at the following URL:

http://mysite.com/mydatalist,aspx

In reality however this is a made up url it does not actually exist anywhere - but is generated dynamically and internally gets converted when needed to something more like:

http://mysite.com/default.asp?tabid=40

And what this does in reality is tell DNN to render the skin and modules associated with tabid 40 -- or page 40 of your site.  Which happens to contain in this case your module to display a datalist.

So to get any other information such as a detail page to display - what you need to do is pass some additional parameters is such a way that makes sense to dnn.

There are a number of ways to do this - but one of the more common is to handle the display of the datalist and the detail page in the same Module.

When you module first opens via a call to  http://mysite.com/mydatalist,aspx there are not additional parameters set - so in your code you would display the datalist.

Now we come to the detail link - in your datalist you would format the actual content of the links something like this:

http://mysite.com/default.asp?tabid=40&dataitem=50 

which can be transformed to DNN friendly urls compliments of NavigateURl

DotNetNuke.Common.Globals.NavigateUrl(this.TabId, "", "dataitem=50")

resulting in a url that looks like this:
http://mysite.com/dataitem/50/mydatalist,aspx

Now in your module you would check for the existance of the query parameter dataitem and if it exists - instead of displaying the datalist instead display the detail information for in this case item 50.

Hope this gives you some food for thought.

Westa