Hi fellow developpers,
I have an existing application that uses ASP (not ASP.NET) to implement INSERT/UPDATE/DELETE actions on a page showing some RECORDS. How difficult is it to port into a DNN module ?

The idea is that the code reduces the need to refresh the page, e.g. displaying detailed data gotten from the <TD> data on the client side and avoids going to the server and avoids even AJAX requests for data . For the said actions, it calls the server only when actually updating the database.

Thanks for the hints.

However, it doesn't seem to work for me. I'll try to explain a simple ASP case:

In Query.ASP, I have a <FORM ACTION="Submit.ASP" METHOD="Post"> and several INPUT tags with information for inserting a record when the user hits <INPUT TYPE="Submit" VALUE="Submit">.

In Submit.ASP, the corresponding data is extracted and the INSERT instruction is created.

These two pages are tested as is, and I can see the data inserted (both with an ASP page and an ASPX page that reads from the same database table.

The fun part is when I put the Query.ASP code into an ASPX page, with <FORM> at the very beginning, and the data input section in a div, when I hit the Submit button, there seems to be some disk i/o, but I can't see the data inserted. There seems to be some basic incompatibility somewhere, but my Script debugger didn't report any error.

Any help is welcome

Whoops! I forgot one big difference between ASP and ASP.NET – ASP.NET uses a single form interface that posts back to itself, not to a new page that knows nothing about the controls on the original page. In addition, ASP.NET ignores controls outside of the first server side form (<form runat="server">) and will raise an exception if you attempt to use multiple server side form tags either declared or coded.

It is very difficult to imagine what you are working with and even more difficult to explain using this medium. Often the code on the receiving page belongs in the sending page itself. Most ASP developers encounter this forms hurdle when transitioning to ASP.NET.

Michael deserves a pat on the back for this one - IFrames may be your best bet as an interim solution.