Re: Access Violation from msado15.dll

From: Brad Wood (b_wood_at_colorflex.com)
Date: 05/29/04

  • Next message: Danny Kellett: "Re: Pooling"
    Date: Fri, 28 May 2004 16:19:42 -0600
    
    

    Confirmed unrelated to D7 update (rollback produced same results). The
    error occurs when I attempt to violate a database constraint, close and
    reopen the connection and try to violate another constraint. I could not
    reproduce in isolation. The same code was handling constraint violations
    just fine for months in a different database...

    "Brad Wood" <b_wood@colorflex.com> wrote in message
    news:40b52ad3$1@newsgroups.borland.com...
    > When executing the ExecProc method of a TADOStoredProc I sometimes get
    > "access violation at address 1F33A7FF in module 'msado15.dll'". All the
    > data passed to the parameters of the TADOStoredProc look fine going in.
    > Subsequent calls to the stored proc give erroneous results (reports that
    > parameters of the stored proc don't exist when they do, actual code
    snippets
    > [C code from somewhere] get inserted into the database). After my
    > application finishes, I get an exception from oleaut32.dll.


  • Next message: Danny Kellett: "Re: Pooling"

    Relevant Pages

    • Re: Is this an error or undefined behaviour?
      ... If a constraint is violated, and an implementation accepts the program anyway, what happens when you run it is not within the scope of the standard. ... Extensions that define the behaviour of constraint violations can't alter the behaviour of strictly conforming programs, nor do they violate other parts of the standard. ...
      (comp.lang.c)
    • Re: Variable structure, constant length allocations
      ... Which constraint do they violate? ... Sorry - that was undefined behavior, not a constraint ... whilst negative array indices do indeed invoke undefined ...
      (comp.lang.c)
    • Re: Jumping into block of an if construct
      ... require a Fortran processor to emit an error message. ... not violate a syntax rule or a constraint. ...
      (comp.lang.fortran)
    • Re: int pointing to char
      ... >> of the code construct that doesn't violate the constraints preceding ... I meant if the semantics of the code implies undefined ... > I don't have a chapter and verse. ... > point of view, though, because of the way constraint is defined. ...
      (comp.lang.c)