Re: Help with Informix/SQL - Novice warning!

In article <3cnf92$qqs@emory.mathcs.emory.edu> ckipp@vth1.vth.colostate.edu (Cathy Kipp) writes:>From: ckipp@vth1.vth.colostate.edu (Cathy Kipp) >Subject: Re: Help with Informix/SQL - Novice warning! >Date: 14 Dec 1994 13:58:42 -0500 >John Pritchard writes: >-> >->We tested and would like to use option 2. What we did not accomplish is >->option 2 using two fields to identify the unique record. For example: >-> >->The table in the application in which we are moving to looks kind of like... >-> org char(16) >-> account char(8) >-> bud1 decimal(12,2) not null >-> bud2 decimal(12,2) not null >-> : >-> : >-> >->The table we build from the old data looks like... >-> org char(16) >-> account char(8) >-> bud1 decimal(12,2) not null >From a design perspective, it looks like you moving from a relational >table to a non-relational table. Is there some reason you're doing >this? Relational databases are generally easier to work with. >Regards, >Cathy Cathy...You are correct in that the design of the appliation is not truley relational (bud1 is the budget for period 1, bud2 is the budget for period 2...) but we are stuck with the third party's application design. The data is coming from an AS400 application...we just loaded it (dbload) into an informix table so we could more easily access the information. What we need is a process for updating a table with data from another table where the tables are related to each other by a combination of two fields. Thanks again... John Pritchard Catalyst Solutions pritchj@ins.infonet.net 712-258-2771