Here's a good one (RBDOS): I had created a form on 2 tables which had an "extra" linking column. Obviously the form did not work the way I expected. I was able to go into the form definition and remove the bogus link. It worked like a charm. A lot of this kind of stuff happens when I inherit the problem from someone else. I this case, I had spent a lot of time designing the form. Once I had removed the bogus link from the form, I was able to rename one column to make things cool for the next time. If I renamed the column before removing the link in the form, the form broke. Saved me a lot of time to have this much control.
-- Dennis McGrath mailto:[EMAIL PROTECTED] -- Productivity Tools for R:Base Programmers http://www.enteract.com/~mcgrath/dennis -- Full time consultant with: SQL Resources Group Steve Hartmann Oak Park, IL mailto:[EMAIL PROTECTED] ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
