Project

General

Profile

Bug #4848

ODBC driver not providing unique identifier to MS Access for a linked table

Added by bford - almost 19 years ago. Updated over 18 years ago.

Status:
Closed
Priority:
Immediate
Assignee:
bford -
Target version:
ODBCng 1.0
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
fixed

Description

MS Access: 2003 SP2
ODBC driver version: Mammoth ODBCng Alpha 1.00.00.01
PostgreSQL: 8.0.1, configured to support SSL

Action: Create an external to link to table db_product. Table definition is below.
CREATE TABLE db_product
( product_id int4 NOT NULL, product_cd varchar(10), product_nm varchar(255), CONSTRAINT db_product_pkey PRIMARY KEY (product_id)
)

Table has a primary key. However, MS Access prompts for the user to select columns for a unique record identifier. Whem the PostgreSQL community driver psqlODBC is used to link the table, MS Access does not prompt for a unique identifier. It appears that the Mammoth ODBC driver is not returning the unique identifier information to MS Access.

#1

Updated by anonymous - over 18 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Also available in: Atom PDF