In my Access(2007) Frontend linked to a SQL Server Backend (2005) application, the SQL Table [SE_MesMatEng] has besides the PK [IdMesMat], a unique indexed column [NumMat].
CONSTRAINT [PK_SE_MatMaq] PRIMARY KEY NONCLUSTERED
( [IdMatMaq] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF, FILLFACTOR = 75) ON [PRIMARY]
) ON [PRIMARY]
CREATE UNIQUE NONCLUSTERED INDEX [IK_SE_MesMatEng] ON [dbo].[SE_MesMatEng]
( [NumMat] ASC
)WITH (PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, FILLFACTOR = 75, ONLINE = OFF) ON [PRIMARY]
However, in the Access FE, the primary key of this linked table curiously shows up on the [NumMat] column instead of the [IdMesMat] column, causing troubles when connecting tables in queries.
Any hint for what to do to get this straight?
Thanks in advance.
CONSTRAINT [PK_SE_MatMaq] PRIMARY KEY NONCLUSTERED
( [IdMatMaq] ASC
)WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF, FILLFACTOR = 75) ON [PRIMARY]
) ON [PRIMARY]
CREATE UNIQUE NONCLUSTERED INDEX [IK_SE_MesMatEng] ON [dbo].[SE_MesMatEng]
( [NumMat] ASC
)WITH (PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, FILLFACTOR = 75, ONLINE = OFF) ON [PRIMARY]
However, in the Access FE, the primary key of this linked table curiously shows up on the [NumMat] column instead of the [IdMesMat] column, causing troubles when connecting tables in queries.
Any hint for what to do to get this straight?
Thanks in advance.