ODBC read only problems

C

C Weigand

Hi
read the Oct 31 post on odbc linked table that became read
only overnight. having similar problems with access 2000
and access 2002. tried all suggestions from Oct 31 post.
was able to create one new db link (odbc) to all tables
with link being successful (all tables read/write). was
able to import all objects EXCEPT my reports. got the
error that the name duplicated an object, project name. am
in a bind. any ideas are appreciated.

CA
 
C

C Weigand

forgot to mention: I am connecting to a microsoft sql
server 2000 over a wireless connection.

CA
 
S

Sylvain Lafontaine

If y understand you correctly, you have a problem with important one or more
report from Access 2000 or 2002 to a new database.

Maybe you should try importing one report at a time to see is someone has a
problem in it. You can also open two sessions of Access and transferring
reports by dragging them or by doing a copy and paste.

Try creating an empty report and importing it. Maybe the error come from an
Active-X object that you have added to your reports.

Make sure also that your references in the VBA options are set correctly and
in the same order. If you have referenced DAO 3.6 then OLEDB in one version
and the inverse (OLEDB followed by DAO) in the other, you can have strange
problems creeping out; especially if you don't have fully qualified all your
databases and recordsets objects with DAO or OLEDB.

Also, the suggestions from Oct 31 post are for linked tables that have
become read only overnight. They won't make read/write tables who have been
read-only from the beginning; except for the suggestion of making sure that
a primary key have been defined for all tables.

S. L.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top