I have had record sets much larger than 2500 records. vb5 is kind of old
though so I would suspect a dll that has been updated and no longer has the
same "meaning" in oneof it's calls. Look the the Dr. Watson. By looking at
the pid you can see what process blew up and then by searching for FAULT you
can see what function blew up. That might give you a clue.
Jim
"Arne Hertwig" <ahertwig_at_quintessence.net> wrote in message
news:9iseiu$o4b$01$1_at_news.t-online.com...
> Hi everybody,
>
> I've a problem with a visal Basic5 application.
> It accesses an Oracle8 Database with ODBC bridge.
>
> The application uses the vb5 database layer (build-in).
> At a big loop through the records with "recordNext" VB-Statement the
> vb.exe process cancels after recordset-count no.2500 and the well known
Dr.
> Watson apears.
> It seems like a magic, because the app breaks always at the same point
> (record).
> The used table has much more than 2500 records.
>
> The config: Win NT 4 SP 6a german, Oracle8 and VB5
> Is there a possible solution? Who is the bad actor (VB runtime, Oracle or
> NT?? another actor??)
>
> thanx in advance, Arne
> Quintessence Consulting GmbH, Arne Hertwig - ahertwig_at_quintessence.net
>
> Zöllners Garten 1, 30900 Wedemark
>
> Tel. +49 (5130) 5888-24 - Fax: +49 (5130) 5888-58
>
> Homepage: http://www.quintessence.net
>
>
>
>
Received on Sun Jul 15 2001 - 12:20:06 CDT
