I'm linking Access tables and receiving #Delete in the table?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Anyone have any idea why this is all the data that's returning when I'm
linking tables to an ODBC db?
But, strangely enough, some are ok....
 
Hi, Michael.

This problem is so commonplace that there are many solutions, depending upon
the version of Access, the version of MDAC, the type of backend database
engine and version, the driver used, and whether the table has a primary
key, whether that primary key is a single column or a composite, whether
that composite primary key allows NULL's, and whether any non-Jet data types
are used (the ones that don't have an identical equivalent in Jet).

Perhaps you have some more information to share so that someone can offer
you advice that might help you?

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.
 
Thanks for the reply Gunny!
The table doesn’t have a primary key and is the 2003 version plus I'm not
sure what an MDAC is?
Also, I'm not sure what driver I'm using - sorry for sound a bit naive....

Michael
 
Hi, Michael.

Place a primary key on every table. If it's a composite primary key, don't
allow NULL's in any column. Then delete your links in Access. (Don't just
refresh the links. The new changes won't be added to existing link
properties. It must be a brand new link so that the Wizard can record the
current table structure.) Recreate the links, and check whether this fixes
it. If not, read on.
The table doesn’t have a primary key
Click to expand...

We can safely eliminate Oracle as being the back end. You're still
breathing. ;-) (An Oracle DBA would never let a non-temporary table be
created without a primary key.) Perhaps you're using SQL Server, MySQL, et
cetera?
I'm not
sure what an MDAC is?
Click to expand...

Microsoft Data Access Components. It's how one software application talks
to the data storage part of another software application. You should have
MDAC 2.8 SP-1 installed on your computer if you're using Access 2003 on
Windows XP. You can check using the MDAC Component Checker, which can be
downloaded from the following Web page:

http://www.microsoft.com/downloads/...f6-4a21-4b43-bf53-14332ef092c9&displaylang=en
Also, I'm not sure what driver I'm using
Click to expand...

Open the ODBC Data Source Administrator and select the "Drivers" tab.
Scroll down until you see the name of your back end database engine. If
there's only one listed for this engine, then you've found it. If there's
more than one, the one being used is stored in the DSN, but you'll have a
hard time reading it. If you're not using a DSN, then you'll have to look at
the connection string, but that probably won't enlighten you.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address so that a message will
be forwarded to me.)
- - -
If my answer has helped you, please sign in and answer yes to the question
"Did this post answer your question?" at the bottom of the message, which
adds your question and the answers to the database of answers. Remember that
questions answered the quickest are often from those who have a history of
rewarding the contributors who have taken the time to answer questions
correctly.
 
Back
Top