A Call to Arms

In this article, Jim Gray and Mark Compton discuss the future of databases. A good view of the progression from primitive database structures → relational databases → the introduction of objects, stored procedures, integration with programming languages → where will it go from here. This is somewhat dense reading; however, it is easy understand even for relative DB-newbies like myself. They give a very good treatment to the ways in which we can look for databases to evolve in the future, including: the tighter integration between programming languages and databases, the changing role of the database as the Internet becomes more dynamic and the needs for information change, and the way in which databases will need to improve in order to handle the tremendous ammounts of data that will be stored, as well as to take advantage of increasingly cheaper storage space and computer. A very worth-while read.


Site run by Andy Smith featuring lots of cool (and free!) ASP.net controls. Controls that I have used so far include:

  • Default Buttons – Assign a button event to fire when a user clicks enter while inside a textbox
  • Dialog Window – Framework for displaying dialog boxes from within an ASP.net app (and receiving return values from the dialog boxes)
  • Expanding Panel – Panel control extended with Javascript so that it can expand and compress without needing to perform a postback
  • First Focus – Assign a specific control to have focus when a page is first loaded

Definitely worth a visit. Lots of useful stuff here.

Transferring Sessions between ASP and ASP.net

As you will find out by doing some quick googling, there is no automatic way to transfer a session between ASP and ASP.net. Some have suggested that you should load the session variables in a database while in the ASP (or ASP.net) portion of the site and retrieve them into a fresh Session object when you are on the ASP.net (or ASP) portion of the site.

Here is something that looks like a better idea. In this article on EggHead Cafe Peter Bromberg describes a different method that covers four pages, 2 ASP and 2 ASP.net:

  1. Load a Session Object in ASP
  2. Server.Transfer to an ASP page. On this page retrieve each entry in the Session object into a hidden form field. Include one hidden field that contains the final destination aspx page. Automatically post this field to a receiver ASP.net page.
  3. ASP.net receiver page. In Page_Load scan the Request.Form object, insert each posted entry to the (new) ASP.net Session object. Server.Transfer to the destination page (listed in one of the posted fields)
  4. Destination ASP.net page. You now have an ASP.net session object that contains all of the appropriate entries for this user

The same procedure can also be reversed to transfer back from ASP.net to ASP. Sample files can be downloaded here.

Doesn’t look too complicated. I think I may give it a try.