|
Michael -
I gave up on Naturally Speaking - mostly because I didn't
have the time to spend on really getting into it...I'll be interested in seeing
how you implement it in version 7 - it's so mouse oriented ... let me
know!
Sami From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Moser Sent: Sunday, March 13, 2005 9:04 AM To: RBG7-L Mailing List Subject: [RBG7-L] - re: When is a one to many form appropriate >> NaturallySpeaking Hi Sami,
Nice to hear from you again, and thanks for the examples.
Your are right, since we stopped being able to edit the links in forms like
we could in DOS one has had to be much more careful about
avoiding unintended matching columns.
How did your experimentation go with NaturallySpeaking? I just
started converting some of my apps to version 7. Once I adjust to the
changes and understand the new options I am going to take a look at
operating the apps by voice with NatSpeak 8. I have been able to speech
implement most other applications I have encountered, including RBase 6.5++, so
it will be interesting to see how it interfaces with RB7.
Thanks, Michael
Michael Moser EXAQ Micro Services www.exaq.com Phone: 916-966-8313 Fax: 916-966-8313 >> Mike - For some good examples, see these forms (and accompanying command >> files) in the ConComp database: ManyToManyTabForm OneToMany >> OneToManyDBGrid OneToManyScrolling One other thing to watch for is >> that tables will be linked on ALL >> same-column names on ALL tables on the form. So be sure that a column >> named "zipcode" for example in the Employee's table is not also named >> "zipcode" in the Client's table if you plan on having the two tables on >> the same form. This has always been >> tr! ue of R:BASE forms, but I thought it was worth a reminder... Sami >> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Michael >> Moser >> Sent: Saturday, March 12, 2005 3:26 PM >> To: RBG7-L Mailing List >> Subject: [RBG7-L] - Re: When is a one to many form appropriate with 3 >> tables - Thanks >> Thanks David, I am going to be doing some conversions and needed to >> understand this setting so as to avoid time consuming and unnecessary >> "glitch repairs". I understand the syntax of the form property much >> better now. I think I can predict and >> select the appropriate one-to-many/many-to-many setting in most normal >> situations (which was my primary need) and can test out the results in >> the rest as required. Thanks for your help, Michael >> Michael Moser >> EXAQ Micro Services >> www.exaq.com >> Phone: 916-966-8313 >> Fax: 916-966-8313 >> >> Not necessarily. I BELIEVE - but I haven't tested this, that if you had >> 3 >> >> tables, Table 1 in one to many to Table 2 and Table 1 in &! nbsp;one to many >> >> with Table 3, that this would be ONE to MANY MANY to MANY means more >> >> than one level of >> >> relationships Table 1 one to many with Table 2 Table 2 one to many with >> >> >> Table 3 David David Blocker >> >> [EMAIL PROTECTED] >> >> 781-784-1919 >> >> Fax: 781-784-1860 >> >> Cell: 339-206-0261 ----- Original Message ---! -- From: Michael Moser >> To: >> >> RBG7-L Mailing List Sent: Saturday, March 12, 2005 3:22 PM Subject: >> >> [RBG7-L]! - Re: When is a one to many form appropriate wtih 3 table s >> >> Hi David, Thank you, that makes sense. Just to clarify then in this >> >> context, in any normalized data schema situation any form with more than >> &nb sp;>> >> 2 tables is going to be a many-to-many form in R:Base 7. This is true >> >> >> because 3 or more tables will always >> >> have "many (more than one) one-to-many" relationships. yes? Thanks, >> >> Michael >> >> Michael Moser >> >> EXAQ Micro Services >> >> www.exaq.com >> >> Phone: 916-! 966-8313 >> >> Fax: 916-966-8313 >> & >> n bsp;>> Michael In &nbs 7.x, the term "Many to Many" on the form >> propert |
- [RBG7-L] - re: When is a one to many form appropriate >&g... Sami Aaron
