Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

Error 3409 when trying to link to SQL Server table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Berean - 29 Feb 2008 18:09 GMT
Hi,

We are using SQL Server 2000 (latest SP) on Windows Server 2003.

Recently we made database changes where we deleted a number of columns from
the highest level table in our database hierarchy (every other table is
either a child or grandchild of this table).

Since we did that we can no linker establish links from Access 2003 to this
table. When we try, we get the following error message:

Invalid field definition <STAMP1> in definition of index or relationship.
(Error 3409)

STAMP1 is our Primary Key field.

None of the fields we deleted were index fields, and none were keys. We have
been racking our brains trying to find the issue but to no avail. Please
help. Thank you.
Sean - 29 Feb 2008 20:16 GMT
A long time ago with access 2003 I ran into a similar problem. What I
had to do was to go into the Access application, delete all of the
linked tables, check the queries/reports, and finally relink the
tables given the names used in the queries and reports. After a
meticulous going over, it worked. I know from using it though, it
seems like everytime you make a change to the strcture (an index, PK,
etc) you have to relink the tables from Access.

Let me know what you find out.

-Sean

> Hi,
>
[quoted text clipped - 15 lines]
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
Berean - 29 Feb 2008 20:40 GMT
Hi Sean,

The effect is happening when anyone tries to link to the SQL Server table,
whether the link was preexisting or not. Even new link attempts generate the
same error.

We have tried rebuilding the indexes on SQL Server and even tried making a
dummy table with the data but no indexes. We could link to the dummy but not
to the one with indexes.

> Hi,
>
[quoted text clipped - 15 lines]
> been racking our brains trying to find the issue but to no avail. Please
> help. Thank you.
Berean - 03 Mar 2008 16:04 GMT
We recently tried rebuilding and renaming all indexes, and are receiving the
same error.

To restate, this is occuring whether we open existing links to Access or try
to build new ones, and only happens on the table we dropped some columns
from.

> Hi Sean,
>
[quoted text clipped - 25 lines]
> > been racking our brains trying to find the issue but to no avail. Please
> > help. Thank you.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.