Linked table in Access shows wrong data

I am attempting to link two tables from SQL server to an access application. Both contain the same column names and the same fields as concatenated primary key but the tables are named differently, have different values and used differently. When these ta
bles are linked in access, one of the tables changes to a single primary key. When this table is opened, you see many duplicates (of what was the concatenated primary key) but the count of records is still equal to SQL Server. When I query in Access for d
uplicates, no results are returned. I drop the table and re-link it, but it still shows a single key. How can I get Access to accept the true table schema?
"bbitzer" <anonymous@.discussions.microsoft.com> wrote in message
news:0219C2D0-5ADB-48E7-86D0-EAC93D9D5422@.microsoft.com...
> I am attempting to link two tables from SQL server to an access
application. Both contain the same column names and the same fields as
concatenated primary key but the tables are named differently, have
different values and used differently. When these tables are linked in
access, one of the tables changes to a single primary key. When this table
is opened, you see many duplicates (of what was the concatenated primary
key) but the count of records is still equal to SQL Server. When I query in
Access for duplicates, no results are returned. I drop the table and re-link
it, but it still shows a single key. How can I get Access to accept the true
table schema?<
On the surface it sounds like a bug... make sure you update your client with
the latest MDAC and Jet updates. Also, on the tables you mention on SQL
Server, be sure that you have added an additional column of data type
timestamp.
Steve

server to Sybase 11 problem

Attempting to create a Linked Server to a Sybase 11 db. Did the following

- Used DSEDIT to create a data source. Ping(Test) works
- Created a System DSN using the Sybase System 11 driver
- Created a Linked Server with following options
General Tab
- Provider as - MS OLE DB Provider for ODBC Drivers
- Data source as the DSN name created above
- No provider string
- Put in the Catalog name
Security Tab
- No local login
- Selected "be made using this security context"
- Specified remote login and password as the Sybase "sa" and pwd
Server Options Tab
- Checked only Collation compatible and Data Access checkboxes

On trying to see the list of tables, got the following error

Error 7399: OLE DB Provider 'MSDASQL' reported an error.
The provider reported an unexpected catastrophic failure.
SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION.SQL Server is termintating this process.

OLE DB error trace[OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x8000ffff: The provider
reported an unexpected catastrophic failure.].

Any solution to this?

HI Mat,

Any response to you query? Even I am facing the same problem. Can you help me out if you have a solution?..

Pls respond to ansathya@.yahoo.com id..

thanks in advance.

Sathya|||We looked into this at is seems like an issue in the sybase provider itself. I'm trying to get a contact there...you folks should try contacting them as well.|||We have got a solution for this from some sources.
Syabase has a known issue on this.

Here are the steps to resolve the problem.

1. In OBDC, while creating the DSN (with the Sybase server name as DSN name) the database name should not be given.

2. In the Linked server properties only the Data source should be given. Remote login (sa and pwd) and in server options only Collation compatible and Data Access are to be selected.

3. The default database for sybase 'sa' login was taken as the user database for which the tables are to be linked.

The above solution works perfectly without issues.

Hope it is helpful to all.
Regards
Geeta