ODBC Access 2002 / SQL Server 2000 Disconnect

ODBC Access 2002 / SQL Server 2000 Disconnect

Post by JerryO » Mon, 24 Mar 2003 14:27:10



We start with a solid DSN Connection to a linked SQL
table.  From the Access table we update 2 fields in
either the SQL table or a View of it.  We can continue
with more successful updates as long as the database is
open.
When we close the Access database, then open it again and
try to do the update, we get Permissions Error 229.  All
permissions are very good - the error happens at even the
highest level.
Workaround code with tabledefs and refreshlinks also
causes the error to happen if we run it.  
I notice that the table appears to still be linked, but
it has been made unupdateable (read-only), where it
definitely was read-write when things work correctly.
When we go back into the database (the error not having
occured) and immediately relink with Tools, Linked Table
Manager before attempting the update, the update will
work.
Once the error has happened, however, the only recovery
is to redo the DSN with the ODBC Administrator.
Can someone help with a suggestion on how to stay linked,
or about what might be happening?
Thanks much in advance.

Jerry OC

 
 
 

ODBC Access 2002 / SQL Server 2000 Disconnect

Post by JerryO » Fri, 28 Mar 2003 03:31:11


Looks like we finally figured out whart was causing the
disconnect - elements in our DSN.
Whether the DSN is on the network or local, it now works
100% of the time without failing.
Two elements in the good DSN we did not have when it
failed are noted with asterisks:

This is the entire DSN:
DRIVER=SQL Server
UID=sunbeam
DATABASE=X2X
*WSID=88888888KW2
*APP=Microsoft Open Database Connectivity
SERVER=SQLXX
Description=X2X Connect

We also intentionally left out the NETWORK and ADDRESS
attributes we had in the failing DSN.

JerryOC

Quote:>-----Original Message-----
>We start with a solid DSN Connection to a linked SQL
>table.  From the Access table we update 2 fields in
>either the SQL table or a View of it.  We can continue
>with more successful updates as long as the database is
>open.
>When we close the Access database, then open it again and
>try to do the update, we get Permissions Error 229.  All
>permissions are very good - the error happens at even the
>highest level.
>Workaround code with tabledefs and refreshlinks also
>causes the error to happen if we run it.  
>I notice that the table appears to still be linked, but
>it has been made unupdateable (read-only), where it
>definitely was read-write when things work correctly.
>When we go back into the database (the error not having
>occured) and immediately relink with Tools, Linked Table
>Manager before attempting the update, the update will
>work.
>Once the error has happened, however, the only recovery
>is to redo the DSN with the ODBC Administrator.
>Can someone help with a suggestion on how to stay linked,
>or about what might be happening?
>Thanks much in advance.

>Jerry OC
>.


 
 
 

1. Transforming Access 2002 SQL to SQL-Server 2000 SQL

High,

I am looking for a tool which is able to transform sql
strings I generated in Access 2002 to a new view in SQL-
Server 2000. I was trying to copy and paste the SQL-
Strings. This is only working with simple views.

What can I do to bring my views from Acccess 2002 to SQL-
Server 2000?

Many thanks for your ideas.

Marcel Grueninger

2. Simple Basic Replication

3. Access 2002 / Access 2000 - Linking via ODBC on local machine

4. Link to an image without embeding

5. Access 2002 Project with SQL Server 2000

6. access97 as front end to SQL 6.5 very slow!!

7. SQL Server 2000 and Access 2002 ADP Project in NT 4.0

8. Where are Proofs that RDB is Subset of OODB?

9. Jumping from Access 2002 to SQL Server 2000

10. Problem in migrating from Access 2002 to SQL server 2000

11. Cannot open tables using Access 2002 adp to SQL Server 2000

12. Access 2002/SQL Server 2000

13. SQL Server 2000/Access 2002 security issue