You could rename the column in a single table view, and use the form against
that view. As long as the form table is a single table view, all
functionality of the underlying table exists, but you can rename the RowID
column (or leave it out) without penalty.
CREATE VIEW EditEmployee +
(EmpRowID, EmpID, FirstName, LastName, ...) AS +
SELECT +
RowID, EmpID, FirstName, LastName, ... +
FROM Employee
If you then hang the form from EditEmployee, you have no problems. Even
where the form is a two table form, the second table will function
correctly, because it is independent, whether or not it is a view. As long
as each of the views called by the form has no WHERE clause, no ORDER BY
clause, and refers to only one table, it is editable. You might even be
able to use a WHERE clause, but I haven't checked that out.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Rommel Relosa
Sent: Tuesday, May 15, 2001 12:11 PM
To: [EMAIL PROTECTED]
Subject: RE: Multiple Table Forms
Tom,
>> Could you change the RowID column of Table A to say... RowIDTabA?
Heh... no. :)
A good number of the tables in the database will have this RowID as a unique
row identifier (as side from using PKs).
The RowID columns are used in a data replication process developed here.
Changing the name of the column (RowID) to be unique across the database
will make the data replication code very difficult to maintain and manage.
I guess a work around would be is to have a "column mapping table" but, that
probably will not help the manageability. We already have a hard time
documenting the replication process... hehehe.
The most feasible work around is using a view for the 2nd table, since not
all tables needed for replication are accessed with a form.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On
Behalf Of Tom Grimshaw
Sent: Monday, May 14, 2001 7:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Multiple Table Forms
Dear Rommel,
This is only a half facetious question...<g>
Could you change the RowID column of Table A to say... RowIDTabA?
Why is it not feasible to change it in table B? (Knowing that may prompt
a work around.)
At 16:14 14/05/01 -0700, you wrote:
>This might not be the right place to post this enchancement request, so I
>apologize in advance.
>
>The scenario:
>
> Table A: (Parent)
> RowID
> TabAColumn1 PK
> TabAColumn2
> TabAColumn3
>
> Table B: (Child)
> RowID
> TabAColumn1 FK
> TabBColumn1
> TabBColumn2
>
>When I place these two tables in a form (wherein Table A is the first
table,
>and Table B is the second table), the RBase engine automatically links the
>two tables with RowID and TabAColumn1.
>
>Would it be possible if the developer gets to "tell" the RBase engine which
>columns to link the two tables in the form?
>
>The work around I have been using is making a view of Table B without the
>RowID column of Table B and using that view as the "second table" of the
>form.
>
>And, no, changing the RowID column of Table B to say... RowIDTabB is not a
>feasible option for the application.
>
>When creating a view, we can specify what columns to link the tables... I
>was just wondering if we can do the same with the forms.
Warmest regards,
Tom Grimshaw
coy: Just For You Software
tel: 61 (0)2 9552 3311
fax: 61 (0)2 9566 2164
email: [EMAIL PROTECTED]
mobile: 0414 675 903
street: 3/66 Wentworth Park Rd Glebe NSW 2037
post: PO Box 470 Glebe NSW 2037 Australia
temp web site: 210.9.46.35
_/_/_/_/_/_/_/_/ _/_/_/_/_/_/ _/ _/ _/_/_/_/_/
_/ _/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/_/_/_/ _/ _/_/_/_/_/
_/ _/ _/ _/
_/ _/ _/ _/ _/
_/ _/ _/ _/_/_/_/_/
