I have a form that is used to update 4 tables as follows: 1st level table - Work order 2nd level table - Procedures (one work order can have many procedures, linked through the work order number) 3rd level table - Manpower (one procedure can have many employees - linked to the procedure table though the work order number and procedure code) 3rd level table - Parts (one procedure can have many parts - linked to the procedure table though the work order number and part number) The lower tables are set up as tabbed form and it works very well. From this form I also can call at least 6 other support forms through buttons; all together, there are several thousand lines of code to support all the EEPs that perform all the necessary operations. The table structure/links that worked in 6.5++ (and previous versions) did not work in 7.0 and I had to modify the table structure/links to work properly in 7.0, I wonder if this is your problem. Javier,
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ====================================================== -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Albert Berry Sent: Thursday, February 12, 2004 3:44 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: table integrity This may help you to diagnose your problem, and it might not. A Client uses a six table form in RBG7. It works fine, displaying subordinate data in each of the five slave tables. Any of the five tables can have no data showing without affecting display of the rest of the slave tables, despite the heirarchy of the forms tables. The trick was to create single table views for each slave table with only the key column that links to master table (Part number, in this case) named the same. Every view renames all the columns other than the part number. Single table views are editable, allowing the user to modify existing data. I still prefer to use buttons that pop up an MDI form for adding new data, and then [Esc] returns to the main form with a forced refresh. Dan <[EMAIL PROTECTED]> wrote: >Ok, > Well, I won't be much help if you have to enter everything for 7 tables on >one form. I use one driving form, then pull up a new form for any new area >that they need to enter. >Dan > > >At 04:20 PM 2/11/2004 -0500, you wrote: >>Yes, I am trying to use the tabbed form for ease of use for the person >>entering data. I need to keep it as simple as possible. If they have to >>close a form and open another to continue with the same record set, they >>will inadvertently omit information. I'm trying to make it as dummy-proof, >>errr... Error-resistant as possible. >> >>-----Original Message----- >>From: Dan Champion [mailto:[EMAIL PROTECTED] >>Sent: Wednesday, February 11, 2004 17:17 >>To: [EMAIL PROTECTED] >>Subject: [RBASE-L] - Re: table integrity >> >> >>Neil, >> Possibly I might be able to help, it sounds as if we have somewhat the >>same sort of table setup. I have 32 tables that keep data for 18,000 >>customers, (Owners) that have 22,000 jobsites (buildings) with over 30,000 >>pieces of equipment... etc. >> >> All billing would point to an owner (custid in the Main table) >> All Jobsite info points to an owner (custid in the Main table) >> All Equipment info points to a Jobsite (Jobid in jobsite table) >> All Service call info points to Jobsite (jobid in jobsite table) etc... >>Not everything points to the main table, yet nothing exists without a link >>back to the main table through a chain of links. >> >>Are you trying to do everything with just one form? >> >>At 01:06 PM 2/11/2004 -0500, you wrote: >>>I am having difficulty linking tables and maintaining referential >>>integrity. I have 7 tables to store information that I need. (down from >>>12) I have separated the information the best i can into the fewest tables >>>I can use. My problem is this....I build a form to enter/edit data. My >>>primary table (the one that everything keys to) will only let me enter >>>data into the primary table and one other table, and be able to recall the >>>info correctly using an outer join. The rest of the tables are locked out. >>>When I go to those fields I cannot enter anything. I have tried a dummy >>>table and this limits me to one table. When I base the form on the primary >>>table I get the above problem. I think my problem lies in my tables and >> >>>how they are keyed. I have read all the examples that come with Rbase and >>>they really don't apply. I'm not dealing with customer products and sales >>>but, rather, addresses, businesses, names and building features. Any >>>suggestions (be nice) would be greatly appreciated. Thank you. >> >> >> >>Dan Champion >>www.championsolutions.net >> > > -- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32 __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need.
