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

[Quoted] Actually, I've just realised that when I get the error mentioned below, if I press 'Cancel' on the error msg box, the C++ debugger starts up, giving the message 'Unhandled exception in VB6.exe(Ora804.dll): 0xC0000006: Access [Quoted] Violation'. I hope this throws new light on the problem. Please help, TIA
Jason

jason wrote in message <7p0nma$3hi$1_at_trinitech.demon.co.uk>...
>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 <37b70566.262016680_at_news.demon.co.uk>...
>>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" <jfielding_at_trinitech.co.uk> 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 ...
>>>>Jason,
>>>>
>>>>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
>SP
>>>>in packages to do our inserts, etc.
>>>>
>>>>Env:
>>>>VB6SP3
>>>>Oracle8.0.5 on HPUX
>>>>ADO 2.10.3711.9 - Could be issue here
>>>>SQL Net 2.3
>>>>
>>>>Mike
>>>>
>>>>jason wrote in message <7op0t2$88b$1_at_trinitech.demon.co.uk>...
>>>>>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
>>>>new
>>>>>record and passes back the new Oracle - generated PK. If I try passing
>>>more
>>>>>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
>read.
>>>>"
>>>>>Which kills my App and VB.
>>>>>The action runs successfully if I limit the number of parameters to 5
>but
>>>>>this no good to me. My largest Fn is only 13 parameters, surely ADO can
>>>>cope
>>>>>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.
>>>>>Thanks
>>>>>Jason
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>-----------------------
>> Dr. Bill Honey
>> Collage Consulting Ltd.
>
>
Received on Fri Aug 13 1999 - 15:25:18 CEST