To Peter Greulich,
Would you pls expound your suggestion.
Thanks for you help 1/12/2001.
In Portugal we have difficulty reading attachments sometimes, I guess due to accent settings etc. I couldn�t read yours.
I got the three tables set up, and working in a set. It works for the first machine only. I suppose I am not getting something simple,
a) what is the purpose of the linking table? In our case, at least, the machine number is the linking field. Thus both of the fields in the linking table will be the same for each record - why have it?
b) You say the second field of the linking table should have table lookup field rule of the machines table, machine ID field. what is that supposed to do?
c) most baffling to me, how is the info of the second (and 3rd,4th,etc)machine number required supposed to get from the contract table to anywhere.
I can see the concept of using lookup rules instead of sets to get over this problem of using the same child db more than once, but isn�t that getting away from the idea of a relational database altogether?
Maybe I have not explained myself.
We write a contract, it has one client, who can rent several different machines.
We have a file of clients. We have a different file of machines.
In the main contract table we have, for example simplified, 3 lines:
-client number: to call the client details, no problem, a one-to-one link to the client table.
-first machine number: to call the first machine from the machine list table.
-second machine number: to call the second machine from the same machine list table as above.
From your info, the second machine number in the contract doesn�t do anything, and therefore doesn�t work.
Thanks again for your help.
Brian.
Would you pls expound your suggestion.
Thanks for you help 1/12/2001.
In Portugal we have difficulty reading attachments sometimes, I guess due to accent settings etc. I couldn�t read yours.
I got the three tables set up, and working in a set. It works for the first machine only. I suppose I am not getting something simple,
a) what is the purpose of the linking table? In our case, at least, the machine number is the linking field. Thus both of the fields in the linking table will be the same for each record - why have it?
b) You say the second field of the linking table should have table lookup field rule of the machines table, machine ID field. what is that supposed to do?
c) most baffling to me, how is the info of the second (and 3rd,4th,etc)machine number required supposed to get from the contract table to anywhere.
I can see the concept of using lookup rules instead of sets to get over this problem of using the same child db more than once, but isn�t that getting away from the idea of a relational database altogether?
Maybe I have not explained myself.
We write a contract, it has one client, who can rent several different machines.
We have a file of clients. We have a different file of machines.
In the main contract table we have, for example simplified, 3 lines:
-client number: to call the client details, no problem, a one-to-one link to the client table.
-first machine number: to call the first machine from the machine list table.
-second machine number: to call the second machine from the same machine list table as above.
From your info, the second machine number in the contract doesn�t do anything, and therefore doesn�t work.
Thanks again for your help.
Brian.
Comment