Re: Oracle and Access 2000 problems

This behavior occurs when ODBC cannot determine the row uniqueness. This issue is discussed in the Scriptoria for Oracle documentation in the Technical Reference section
(http://www.bunkerhill.com/Scriptoria%20for%20Oracle%20files/User%20Guide%20 HTML/UserGuide.htm) Search for #DELETE to find a detailed explanation and work-around.

HTH,
Ron in NY

"Angela" <angelah_at_fiddle.sph.unc.edu> wrote in message news:3A1565EC.391A2061_at_fiddle.sph.unc.edu...
> Hi,
>
> I'm developing a database on Oracle 8.15 on a Solaris 2.6
> platform. I'm using the Oracle ODBC driver ver. 8.01.05.
> Everything works fine when I enter records using SQL*Plus or
> through an Access97 interface. However, when I try to use
> Access2000, everytime I enter data, it looks like its fine
> going through ODBC to Oracle, but when I click refresh on
> the spreadsheet window, the newly entered row of data has
> "#deleted" in all the fields. It only happens to the new
> row. It doesn't affect any of the existing rows. If I
> close out of the spreadsheet view, then come back in, all
> the data is there with no #deleted. I check using SQL*Plus,
> and everything looks fine.
>
> I don't want the users to see this error when they enter
> data. I've tried using the MS Knowledge Base articles, but
> none of their fixes have solved my problem. I thought it
> could be my autogenerating number sequence b/c there was no
> precision indicated (number, changed to number(10)). Access
> only understands number precision up to 28, while Oracle can
> go up to 38. However, changing the precision didn't help. I
> tried giving precisions to all my number fields and/or
> changing unneeded number fields to varchar2, but it still
> didn't work.
>
> I have mostly varchar2 fields, with three date fields, and 3
> number fields (number(4,2), number(10) primary key,
> number(2) foreign key).
>
> I've done an ODBC trace to see what happens. It was
> difficult to understand some of the codes, but I found that
> after a record is passed to Oracle, it looks like when it
> gets passed back (SQLFetch) to Access, an SQL_NO_DATA_FOUND
> error occurs. However, it looks like it continues on
> (SQLFreeStmt) and succeeds with that operation.
>
> Anybody have any idea on what I can do to get my oracle db
> to work with
> Access 2000?
>
> Thank you for your help,
> Angela
Received on Wed Nov 22 2000 - 00:52:53 CET