Access ODBC Database Link Problems With XP Professional

Access ODBC Database Link Problems With XP Professional

Post by Jeff Grego » Thu, 15 Jul 2004 22:41:27


In the past I had a Windows ME computer and linked via
ODBC connection to an AS400 file with no problems. Since
I have a new computer with windows XP, I can still link
to the AS400 and many files work, but one file keeps
getting garbage. I get a few lines of good data, but the
other lines have all "#Deleted #Deleted #Deleted" in
the fields.

I am not sure if this is a problem with the XP
environment, or if when I reinstalled Access I did not
set up my ODBC connections properly.

Any help in getting to the root of the problem would be
appreciated.

Thanks,
Jeff Gregory
 
 
 

Access ODBC Database Link Problems With XP Professional

Post by Rick Brand » Fri, 16 Jul 2004 11:10:21


This can be a few things. Making sure you have the latest ODBC drivers is
always a good start. When you link to AS400 tables that have no Primary Key you
are asked to specify columns that Access can use to build a unique index with
for updates. In some cases I have seen where selecting the wrong columns caused
this. Also if any of the fields making up the unique index are of a DataType
that Access has no direct matching type can cause this.

If you don't need updatability, a Passthrough query will usually not have this
problem.


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

 
 
 

Access ODBC Database Link Problems With XP Professional

Post by Jeff Grego » Fri, 16 Jul 2004 22:10:06

Thanks for the reply. Unfortunately none of the
solutions for the ODBC Table Update worked. The ODBC
connection is actually an IBM solution and I could not
find an update. I did get a Microsoft update, but that
did not help. The database came from my old computer and
worked on my old computer (with ME) so theoretically it
should work the same with the XP environment.

The passthrough query was a great solution and is a nice
work around. I was not aware that existed.

Thanks again.
Jeff Gregory


Since
the
latest ODBC drivers is
have no Primary Key you
build a unique index with
the wrong columns caused
index are of a DataType
usually not have this