C
Christoffer Vig
Using Access 2000 adp to connect to a SQL Server 2000.
The application has been running well for over a year.
There have been continous development and fixing on both the
views/tables on the server, and on the Access part.
There were some strange problems after installation of SP3, related to
what queries were determined updatable according to Access. Access
suddenly found some queries to be unupdatable, the fix here was to
modify the query to include the primary key from the updatable table
only - in the select statement I had to remove the primary key from all
joined tables.
Now, after I modified some queries, there is a weird error
on entering some forms.
The error is Error 2101 "The setting you entered isn't valid for this
property"
The error occurs on the statement:
Uniquetable="update_this_table"
It appears this whole Uniquetable statement is unnecessary. As there is
enough information in the view to find out what the updatable table is
(it is the only one with a primary key). (???)
The fix in this case was to remove the UniqueTable assignment.
But why? What happens? Why does it say Error 2101??
I have searched around and have not been able to find anything at all
related to this weird behaviour.
Can somebody tell me what happens?
best regards
Christoffer
The application has been running well for over a year.
There have been continous development and fixing on both the
views/tables on the server, and on the Access part.
There were some strange problems after installation of SP3, related to
what queries were determined updatable according to Access. Access
suddenly found some queries to be unupdatable, the fix here was to
modify the query to include the primary key from the updatable table
only - in the select statement I had to remove the primary key from all
joined tables.
Now, after I modified some queries, there is a weird error
on entering some forms.
The error is Error 2101 "The setting you entered isn't valid for this
property"
The error occurs on the statement:
Uniquetable="update_this_table"
It appears this whole Uniquetable statement is unnecessary. As there is
enough information in the view to find out what the updatable table is
(it is the only one with a primary key). (???)
The fix in this case was to remove the UniqueTable assignment.
But why? What happens? Why does it say Error 2101??
I have searched around and have not been able to find anything at all
related to this weird behaviour.
Can somebody tell me what happens?
best regards
Christoffer