| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Too Much Data??? Oracle --> MS-Access
Tracy
This could be a problem with ODBC that's documented in the MS Knowledgebase (search under "Oracle" and "ODBC"). It tends to happen if the table's primary key includes a field that contains an ORACLE Number type that can't be represented with full precision by Access. You tend to find if you look at the linked table in Design view that Access has mapped these fields onto a Double type rather than an integer or long.
Typically you find that linked tables display correctly if the key field contains small numbers, but won't if it contains larger numbers. For example, we have a database whose primary key in Oracle is Number(10). This field appears as a Double in design view when the table is linked to Access. If the key field contains (say) numbers up to 100, there's no problem; if you put 1000000 into the key field, you just see #Deleted.
HTH
In article <36092CBA.5271_at_redrockgrp.com>, tlp_at_redrockgrp.com writes
>Any help on the following is much appreciated!:
>
> I have a back-end Oracle database. I'm trying to "link"
> the (table) data into an Access database.
>
> The table is showing the columns with the data being displayed
> as #deleted#. I've seen this error before for various reasons.
>
> What it is not:
>
> - Permissions on the data are fine
> - I've 'imported' the data into an Access table fine
>
> I've 'linked' in other *smaller* tables. I'm assuming its just
> too much data. Is this a limitation of Access? Memory? Oracle
> or SQL*Net?
>
> I'd like to know if its something I can address or I need to
> find a work-around - importing doesn't seem all that reasonable
> to me..
>
> Again, appreciate any thoughts or info!
>
> --tl
>
>--
>Tracy Lynn Pendergast tlp_at_redrockgrp.com
>Independent Consultant Database Specialist
>(212) 665-2396
 |
 |