A one tier architecture is an architecture where the data is stored on the own computers harddrive or on a cd-rom. The two tier architecture, or client/server architecture, were developed in the 1980’s. It made it possible to connect computers to each other in a network and to get access to other peoples’ data, programs/applications and hardware (for example printer). This technology had a lot of advantages, such as sharing data between several users or modify the system to fit a special area. The client in this system is the one who requests a favour and the server is the part who answers the request. An obvious problem that the client/server architecture had, was that the server became overloaded when there were too many users connected to it. The three tier architecture was developed in the mid 1990’s in order to improve the overload problem. A middle tier was developed that could handle hundreds of users by queues, application-executions or the establishment of databases. This tier improved the flexibility, maintenance, reuse and prestanda by centralization. Yet another improvement with three tier is the capability of developing the different tiers in different programming languages. Several different techniques exist to implement three tier architecture. We will cover Microsoft’s Active Server Pages and ActiveX Data Objects together with Netscape’s LiveWire in this paper. We have also done a comparison between ASP and LiveWire. The result from that study was based on own conclusions, studies and answers from the persons we have interviewed. The result from our studies is that the techniques are very similar when it comes to creating applications, but they differ in what script language they apply, compatibility to other platforms and the database connection. We believe that these techniques will maintain popular some years but then they will be replaced by object oriented techniques like JAVA and JSP, where several tiers may are involved.