Member Avatar for zaman1111

We were successful on linking the table from MS access to Oracle 10g, but we dont see any data in the MS access linked table. It shows as data #deleted. Can you please describe how we can see those datas.

  • 3 Contributors
  • 3 Replies
  • 213 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by weilander

Dani AI

Generated

Several posters in this thread (, , ) report the same two symptoms: linked Oracle 10g tables in Access show rows as “#Deleted”, and there’s a numeric precision/scale error. Those symptoms most often trace to one of two root causes: Access can’t obtain a stable unique row identifier for the linked table, or one or more column types/precision values don’t map cleanly across the ODBC driver. (A registry/encoding tweak was suggested earlier; treat client registry edits as a last resort and test on a non‑production machine.)

Practical checklist (work through these in order):

  • Verify the DSN/driver works outside Access. Use the ODBC Data Source Administrator or MSQRY32/SQL*Plus to run a simple SELECT and confirm rows and types return correctly.
  • If the table has no declared primary key or Access never prompts for a unique identifier, create a view that exposes a stable identifier (ROWID) and link the view instead. Example:
CREATE VIEW vw_for_access AS
SELECT ROWID AS ora_rowid, t.col1, t.col2, t.col3
FROM mytable t;

Link that view in Access; when the wizard asks, choose ora_rowid as the unique record identifier.

  • If a numeric precision/scale mismatch is causing errors, either increase the Oracle column precision or cast the column in a view to a broader type before linking. Example alter and cast patterns:
ALTER TABLE mytable MODIFY (amount NUMBER(10,3));

-- or in a view:
CREATE VIEW vw_for_access AS
SELECT ROWID AS ora_rowid, CAST(amount AS FLOAT) AS amount_float, ...
FROM mytable;
  • Exclude unsupported columns (LONG, LOBs, complex types) in a view if you only need the simpler columns in Access.
  • Confirm driver/client compatibility: Access 2003 is 32‑bit, so use a matching 32‑bit Oracle client/ODBC driver; try the Oracle OLE DB provider or a different ODBC driver if problems persist.

These steps resolve the vast majority of “#Deleted” and precision-mapping cases: give Access a clear, stable identifier and make sure every linked column maps to a supported type/precision.

Member Avatar for dbugme

Was there any answer to this. I'm having the same problem. Using AccessXP, I can link to Oracle Tables via Oracle 10g ODBC Driver. But when I open the table all values in fields are displayed as "#deleted". The weird thing is if I connect to the same table using MSQRY32.exe everthing displays correctly.

Member Avatar for weilander

I have the same kind of problem.

The error message: The decimal field's precision is too small to accept the numeric you attempted to add.

The oracle-field is: NUMBER(6,3)
In Access the field is: Decimal (6,3).

Can someone tell me how to solve this problem?

Member Avatar for weilander

To fix this, go to registry,

change all "HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEx\NLS_LANG to "AMERICAN_AMERICA.WE8ISO8859P1".

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.