Re: Three-tier architecture with MSAccess as Client !?

Ok, normally I don't attempt any responses here, being an Informix beginner myself (having heeded earlier posts about being sure of your grounding before posting ;) But application architectures I do know a little about, so I'll offer a bit of input... The scenario you propose isn't really a three-tier architecture, when the DB Server (using triggers) is doing the application logic processing. For a good explanation of three tier vs. other architectures, check out http://www.sei.cmu.edu/str/descriptions/clientserver_body.html One GB of data per year isn't really that much. More than you'd want to consider handling with Access to be sure, but a piece-o-cake for any *real* DBMS. Presumably, since you discuss the DB and application on the same server, you're using NT, and I can't say with any certainty whether or not I4GL can compile into .DLL's that you can use with Access. Maybe someone else on the list can tell you that. From my experience with DB engines, if you need fast calculation, you won't want to use triggers for that. While the DB excels at data storage and retrieval, adding almost any manipulation can slow things down significantly. This is where the middle tier should come in, assuming you mean calculations in the sense I'm interpreting. I'd certainly consider using C for this part, were I facing such a project. Of course, it goes without saying that there's lots I don't know about your particular situation, so that might not be your best bet. HTH, Martie "C. Fischer" wrote: > > Three-tier architecture > > Aim: > 1. Fast calculation of an offer/product. > The products must be configured, that is the reason > why calculating is so difficult. > 2. Creating something like a data-mart. > > Problem: > More than 1 GB of data each year. > A lot of server-side application is needed (to calculate). > The client need some intelligence, too. > (I think this model is called Distributed Business Logic) > > Idea: > 1. Database and application on one machine. > But with the possibility to scale the system in the future > by dividing the app- and the db-part. > So both parts must be separated logically from the beginning. > > 2. MSAccess as client is preferred by the customer. > > One Scenario could be like this (perhaps) > 1. User enters the offer-relevant data (customer, product, > some product-specifications...) in MSAccess. > (MSAccess generate an INSERT INTO statement with > the entered data) > 2. The application-server begins (TRIGGER) the calculation by using > the tables of the db-server (materials, bill of material, > customers...) and generates the result. > 3. The result is presented by the MSAccess-Client. > (via ODBC) > > Questions: > (I am Informix-beginner) > I recognized that Informix dynamic 4gl exsist, but I have no > idea how it works. > Is it a normal database only with code in it? > > I did not found a complete language-reference. > What can be programmed and what is not possible? > (I have seen SPL do not know a CASE-structure eg.) > > Any ideas or comments? > bye > cf >