Re: VB6 SP3 / ADO2.1 /Ora 8 - "Error - Memory could not be written"

From: jason <>
Date: Fri, 13 Aug 1999 10:14:44 +0100
Message-ID: <7p0nma$3hi$>

[Quoted] No - no filters, but if you have any pointers on tracking down memory leaks - you know that VB would then stand for Vouchers for Beer.

Bill Honey wrote in message <>...
>Are you setting a filter by any chance ?
>I'm getting the same problem with SQL server 7.0 when I set a filter.
>Looks like a memory leak in ADO somewhere. How to find though ...
>"jason" <> wrote:
>>OK - call me dumb, but can you tell me how I find this out.
>>If it's any help, I use a DSN in my Connect String which references an MS
>>ODBC for Oracle driver (2.573.4202.00).
>>Mike Sprague wrote in message ...
>>>Are you using the ODBC OLEDB provider or the Oracle OLEDB provider?
>>>We are using the Oracle provider and not having any problems with using
>>>in packages to do our inserts, etc.
>>>Oracle8.0.5 on HPUX
>>>ADO 2.10.3711.9 - Could be issue here
>>>SQL Net 2.3
>>>jason wrote in message <7op0t2$88b$>...
>>>>I'm trying to insert records (using VB6 SP3 and ADO 2.10.4202.1) via a
>>>>Stored Function into an Oracle 8.0.4 DB. The Fn is supposed to inserts a
>>>>record and passes back the new Oracle - generated PK. If I try passing
>>>>than 5 parameters to the Fn - VB blows with - "at 0xXXXXXXXX referenced
>>>>memory at 0xXXXXXXXX. The
>>>>memory could not be written. " This is followed by the error - "at
>>>>0xXXXXXXXX referenced memory at 0xXXXXXXXX. The memory could not be
>>>>Which kills my App and VB.
>>>>The action runs successfully if I limit the number of parameters to 5
>>>>this no good to me. My largest Fn is only 13 parameters, surely ADO can
>>>>with more than 5 by now ?? .Is there another method of doing this or a
>>>>Command Property I can set ?
>>>>I've also tried this using an Stored Proc within a Package - same thing
>>>>Please Help !!
>>>>Any suggesetions are much appreciated.
> Dr. Bill Honey
> Collage Consulting Ltd.
Received on Fri Aug 13 1999 - 11:14:44 CEST

Original text of this message