OraOLEDB Accessor is not a parameter accessor

[Glenn_Suggs]

Hi all... I'm having a problem reading a back-end table and I hope to find a solution. I've never seen this error before and it's probably related to the back-end database but I think maybe someone here may have seen it before. I'm trying to read a table in ADO that seems to have problems with two "date" fields and both raise this error only on certain records and independantly of each other. The error is: Error -2147217845 was generated OraOLEDB Accessor is not a parameter accessor at line# 800. The error is part of my generic error routine of course but hopefully the meaning is apparent. Thanks in advance for any help and responses on this issue. ...Glenn

[June7]

Disable the error handler and let the debugger stop on the line of code that triggers the error. Check status and content of variables. Identify circumstances causing the error.

[Glenn_Suggs]

I have done as you suggested with the same results, only the error displays in native Access format with a Debug option. Run time error '-2147217845 (80040e4b)': Accessor is not a parameter accessor. When I click the Debug button, the date field displays nothing, not even null and the other fields on the record I debug.printed had values just fine.

[June7]

So what is it about the records that are different? You say date field displays nothing, did you mean a date variable? If there is a date value in the record, how can it not be available in the recordset?

Would have to review data and code to analyse issue.

This is a split db? What is the backend?

[Glenn_Suggs]

The backend is Oracle. My ADO code reads and debug.prints over 15,000 records and then it hits the bad date, stops, and when I hover the mouse over each record field that is debug.printed, the bad date field shows no value at all and the others that I've included in the debug.print look fine. Also, the column with the bad date prints okay until it hits the bad one. Not enough to go on, I guess. The code I'm using to read the table is the same as some I've used many, many times. Also, the table is part of an application that crashes when it tries to access any of these date fields. Maybe a question for the DBA?

[orange]

the column with the bad date prints okay until it hits the bad one.

What is the value of a Bad one? That is, what exactly is a bad one???

[June7]

I am not familiar with Oracle. Could individual records be corrupted?

Yes, talk to the DBA.

[Glenn_Suggs]

The "Bad One" is blank. No value whatsoever. Not an empty string. And not null. And it throws the aforementioned error.

[Glenn_Suggs]

Mainly by contact with Oracle is only as a back-end. So, as I said, the error is new to me, also. I'll talk to the DBA.