Form using 2 Table View Not updateable

  • Thread starter Thread starter Andy Calder
  • Start date Start date
A

Andy Calder

Is there a method where you can create a form that is
based on a view that has 2 tables and that allows you to
make changes to the data using the form? I tried it and it
says the form is not updateable because the 'Unique table'
property is not set. I try to set the 'Unique Table'
property but it says the entry is not in the list.
Most forms are based on more than 1 table so there has to
be a way to allow data entry/changes in forms when using
ADP's!

Any Ideas

Thanks
 
Hi Andy,
property is not set. I try to set the 'Unique Table'
property but it says the entry is not in the list.
Click to expand...

The property "unique table" needs the entry of one
of the source relations from within the view.

Therefore you have to programm a workaround because
of the owners problem. The problem occurs as follows:

If you have created a view as the dbo role and you are
connected with your adp as 'dbo' you will not be able
to set the unique table with the full naming qualifyer
like 'dbo.myTable' but without the name of the owner.

If you are connected to the database as another user
you HAVE to use the full qualifyer like 'dbo.myTable.

To solve this problem you should set the property 'unique
table' by code depending on the owner of the objects
in your view.

HTH ;-)

--
Gruß, Uwe Ricken
MCP for SQL Server 2000 Database Implementation

GNS GmbH, Frankfurt am Main
http://www.gns-online.de
http://www.memberadmin.de
http://www.conferenceadmin.de
____________________________________________________
APP: http://www.AccessProfiPool.de
dbdev: http://www.dbdev.org
FAQ: http://www.donkarl.com/AccessFAQ.htm
 
Uwe said:
Hi Andy,




The property "unique table" needs the entry of one
of the source relations from within the view.

Therefore you have to programm a workaround because
of the owners problem. The problem occurs as follows:

If you have created a view as the dbo role and you are
connected with your adp as 'dbo' you will not be able
to set the unique table with the full naming qualifyer
like 'dbo.myTable' but without the name of the owner.

If you are connected to the database as another user
you HAVE to use the full qualifyer like 'dbo.myTable.

To solve this problem you should set the property 'unique
table' by code depending on the owner of the objects
in your view.
Click to expand...

Also remember to select the primary keys of *all* tables. Not just the
one you want to update. This seems to apply only if you are using MDAC
version 2.7 or later. Pre. 2.7 you could be happy with only the primary
key of the 'Unique table'.

The documentation is somewhat sparse on this point, I think.

chris
 
Back
Top