>From your description I would consider this a one-tier architecture. Ussually the tiers are defined as follows:
- Presentation GUI, all user interaction. - Business Logic Logic, which can not be expressed by constraints in the database. Interaction with other (software) systems and some more logic. - Data (access) layer This one is hard IMHO. In most cases this resembles a mapper, which maps from relational tables to objects used in the business logic. Additionally you have a set of predefined functions, which perform queries upon the data sources and return the results as objects. In most cases these are only access layers, which use a database server and stored procedures. HTH, Mike -----Ursprüngliche Nachricht----- Von: John Newby [mailto:[EMAIL PROTECTED] Gesendet: Montag, 7. August 2006 16:43 An: sqlite-users@sqlite.org Betreff: [sqlite] what tier architecture? Hi, this is probably a stupid question and it has nothing to do with SQlite per se so I apologise in advance for hijacking the emails withmy question plus I don't even know if this is the right place to ask the question. I have created a GUI to SQLite using VB.Net for my University project and it interfaces with the SQLite .dll file. I have to now write about the architecture of my product but I am unsure as what it would be, after reading this website I am even more confused :- http://www.javaworld.com/javaworld/jw-01-2000/jw-01-ssj-tiers.html Could it be one tier as both the DBMS and GUI are as one or could it be two tier as the GUI could be the client and the DBMS the server or could it be three tier as the GUI could be the client and the DBMS the server and database? I'm really confused, so any help or information on this subject would be really appreciated. Many thanks John
