LISTSERV - HP3000-L Archives

HP3000-L Archives

April 2002, Week 5

HP3000-L@RAVEN.UTC.EDU

	LISTSERV Archives
	HP3000-L Home
	HP3000-L April 2002, Week 5

	Log In
	Register

	Subscribe or Unsubscribe

	Search Archives

Options:	Use Monospaced Font Show Text Part by Default Show All Mail Headers
Message:	[<< First] [< Prev] [Next >] [Last >>]
Topic:	[<< First] [< Prev] [Next >] [Last >>]
Author:	[<< First] [< Prev] [Next >] [Last >>]

Subject:	ODBC connection crashes with "Bad row header"
From:	ILYA BOGORAD <[log in to unmask]>
Reply To:	ILYA BOGORAD <[log in to unmask]>
Date:	Tue, 30 Apr 2002 14:47:23 -0500
Content-Type:	text/plain
Parts/Attachments:	text/plain (26 lines)

Folks,

Some urgent wisdom is required!
I've got an MS Access application that downloads data from a
TurboImage database on MPE every night. It has been working with no
probs up until last night when the extract process crashed.

Upon investigation, I am finding that a simple select from one of the
tables aborts with "Data Transmission Error: Bad row header (#-34)".

I moved that piece of code into a pass-thru query. When I run it, it
happily shows a few thousand records, but if you scroll far enough to
a PARTICULAR record, it bombs out with the aforementioned message.

I am using the standard ODBCLINK/SE driver.

What is this ??? A corruption ? MB Foster site refers to "command
timeout" and "sort timeout", but I don't have that in my ODBC setup.

Any help is greatly appreciated.

Ilya

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2

RAVEN.UTC.EDU