Error 3146 - ODBC Call failed

[Niranjan]

Hi everyone
We just upsized to SQL server (Access 2003 front end). I am running
into error 3146 on a particular table. Part of my code, I have a
simple delete SQL statement and I am getting an error on this
statement.

CurrentDb.Execute "Delete * from [Raw Import Table];", dbSeeChanges

Raw Import Table has a PK (ID - Autonumber).

Does anyone know how to fix it?

[Laurenz Albe]

Easy, just use Oracle instead.

You have come to the right group!

Yours,
Laurenz Albe

[DA Morgan]

SQL Server is not an Oracle product so we can not help you with
your current issue using your existing RDBMS. But if you were
to move to Oracle with a real front-end such as HTML_DB, a substantial
improvement by almost any measure, the issue would not exist.
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damo...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

[Mark D Powell]

On Dec 30, 12:00 pm, DA Morgan <damor...@psoug.org> wrote:
> Niranjan wrote:
> > Hi everyone
> > We just upsized to SQL server (Access 2003 front end). I am running
> > into error 3146 on a particular table. Part of my code, I have a
> > simple delete SQL statement and I am getting an error on this
> > statement.
>
> > CurrentDb.Execute "Delete * from [Raw Import Table];", dbSeeChanges
>
> > Raw Import Table has a PK (ID - Autonumber).
>
> > Does anyone know how to fix it?
>
> SQL Server is not an Oracle product so we can not help you with
> your current issue using your existing RDBMS. But if you were
> to move to Oracle with a real front-end such as HTML_DB, a substantial
> improvement by almost any measure, the issue would not exist.
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington

> damor...@x.washington.edu (replace x with u to respond)

> Puget Sound Oracle Users Groupwww.psoug.org

Let it not be said that those of us on the Oracle newsgroup do not
always try to be helpful:

The 3146 is a catch all error that masks the real problem. Here is
one known issue where SQL Server database settings can cause the issue
and documents on the error and how to get more information.

PRB: DAO Run-Time Error 3146 When Modifying SQLServer Data
http://support.microsoft.com/kb/195225

How To Get More Information on the ODBC Call Failed Error
http://support.microsoft.com/kb/154510

Trappable Microsoft Jet and DAO Errors
http://msdn.microsoft.com/en-us/library/bb221208.aspx

HTH -- Mark D Powell --

[sylvie....@gmail.com]

This run-time error 3146 occurs when the SQL server cannot return any number for a statement. When the servers unable to return a message which indicate the number of rows which is affected by the statement to be ready to execute. You have to SET NOCOUNT ON because it prevents SQL Server from sending DONE_IN_PROC messages for each statement which is executed in the store procedure.
http://www.r6034runtimeerrorfix.com

[sylvie....@gmail.com]

[sylvie....@gmail.com]

[joel garry]

On Tuesday, March 4, 2014 1:54:30 AM UTC-8, sylvie....@gmail.com wrote:
> This run-time error 3146 occurs when the SQL server cannot return any number for a statement. When the servers unable to return a message which indicate the number of rows which is affected by the statement to be ready to execute. You have to SET NOCOUNT ON because it prevents SQL Server from sending DONE_IN_PROC messages for each statement which is executed in the store procedure.
>
> http://www.r6034runtimeerrorfix.com

Welcome to the group!

A couple of things to keep in mind:

This is an Oracle group, so SQL Server questions are off topic.

If you respond to a very old thread, you may look silly. Please check the dates of what you are responding to.

Everyone makes mistakes, the smart people learn a positive lesson from them.

jg
--
@home.com is bogus.
http://www.forbes.com/sites/oracle/2014/03/04/see-oracles-sci-fi-movie-cloud-odyssey-at-exclusive-screenings/