Hi Razzak, Can you think of a scenario where you would want:
1. A 2 table form to be many to many? 2. A 3 or more table form to be one to one? If the answer to scenarios 1 and 2 are both "NEVER" then the form designer should manage this behind the scenes, and we should never see the option, so we can't mess it up or miss that "detail" If the answer to either scenario is "MAYBE" we need to know exactly how these options would change the form behavior in each of the above scenarios so we can use them effectively. My 2 cents Dennis McGrath -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of A. Razzak Memon Sent: Friday, May 30, 2008 1:17 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: conversion anomoly At 01:09 PM 5/30/2008, Dennis McGrath wrote: >Dawn, > >That was it! > >LOL! I check the help and it is not much help. > >What exactly does the "one to many" option do? The result >definitely does not look logical to me in any way. The help >does not tell me anything useful! Dennis, Glad to hear that you are finally catching up to Windows! I'm sure it is shocking as well as a challenge for you. For the benefit of the list, in a multi-table form, the table relationship is determined by associating the tables. When there are only two tables involved, the "one-to-many" relationship is the default. However, if you have more than two tables involved, the "many-to-many" relationship is the appropriate option. The Help states: . One to Many Determines that the logic of the form will follow a One to Many relationship . Many to Many Determines that the logic of the form will follow a Many to Many relationship If you do not know the "One To Many"/"Many to Many" relational logic of your form, how can we possibly put that in the Help? If one does not understand what "One To Many" or "Many to Many" means, (... ready for this?) then one can search the Help! Very Best R:egards, Razzak.
