Invalid Variant Operation

From: Matthew Pascoe (mpascoe_at_stocklogix.com.au)
Date: 09/23/04 

Date: Thu, 23 Sep 2004 09:05:37 +1000

I have a stored procedure in SQL Server 2000 that I am calling from a D5
app.

The SP starts a transaction, updates various tables and then commits the
transaction.

When I am testing this with 2 client PC's calling this same SP at exactly
the same time, every now and again if the timimg is just right, one of the
PC's get a message saying 'Invalid Variant Operation' and the update is
rolled back. The updates on the other PC get committed fine.

This error will only ever occur in the above scenario so seems to be some
sort of contention problem.

Can anyone help me out with this?

Thanks for any advice.

Matthew

Relevant Pages

  • RE: Master/Detail Transactions
    ... If any of the updates fails, ... pending parent and child rows within the scope of a transaction, ... cascade newly retrieved parent identity values down to pending child rows ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Recordset.AddNew and the recordset objects data retaining
    ... I absolutely think that in extremely large jobs, ... I know, I could send a single transaction containing 10,000 records but it ... > physical memory to accommodate the TWO sets of 100,000 records: ... >> The statement you make about the individual updates not hitting the ...
    (microsoft.public.data.ado)
  • Re: Recordset.AddNew and the recordset objects data retaining
    ... The statement you make about the individual updates not hitting the database ... to do with the updates being in a transaction but rather on whether you specify ... spill over and the memory starts paging out to disk that concerns me). ...
    (microsoft.public.data.ado)
  • Re: Using transactions to insert into to a table while allowing read access to existing data
    ... purpose but to roll back the transaction. ... rows with uncommitted updates are marked with locks. ... isolation level is READ COMMITTED, ... then finally committing the transaction. ...
    (microsoft.public.sqlserver.programming)
  • Re: Cant use autonumber
    ... Another respondent has pointed you to his own answer. ... As for wrapping multiple updates into a single transaction: ... >> you can wrap that update into the transaction used by the bound form. ...
    (microsoft.public.access.formscoding)