[RBG7-L] - Re: DBGrid Form

[Doug Hamilton]

Razzak, I have a question about the issue of unintentional table linking 
via columns in forms.  It has come up before and as you pointed out, the 
best way to avoid it is through good database design.  A workaround is 
to use views and aliases (aliaii?) or rename the columns.  These can be 
accomplished with varying degrees of effort and success, especially if 
we've inherited a database with faulty design.  

How feasible would it be to allow us to define the linking columns 
between tables in the form definition, probably under Tables | 
Add/Remove Tables.  That way we could link tables on specified 
same-named columns.  We could also link tables on differently named 
columns, much like we do in WHERE clauses.  And since we'd be working 
directly with the tables instead of views, the data would all be 
editable.  (I'm assuming multi-table views are not editable.)

Just wondering.  I'm sure there are reasons it's not been done yet, so I 
apologize if I've overlooked some obvious shortcomings.

Thanks,
Doug
A. Razzak Memon wrote:
At 06:29 PM 2/20/2005, Dick Fey wrote:
A. If there are other common columns in the tables, does the data 
have to match?

Yes!
That's the rule of R:BASE matching apples to apples.

B. Does it matter if the common columns other than Refnum are 
included in the
grid or not?

No.
Matching is done at the table/column level, not what you show in the 
form/grid.


C. Is there some way you have to tie them together?  as you tie a 
view together

Yes.
Either RENAME other (non-matching) columns or base your form on a VIEW 
with
ALIAS names for non-matching columns

Its a great idea, but no luck so far at making it work.

Normalize your database!
Very Best R:egards,
Razzak.