HP3000-L Archives

October 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

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 >>]

Print Reply
Subject:
From:
Therm-O-Link <[log in to unmask]>
Reply To:
Therm-O-Link <[log in to unmask]>
Date:
Thu, 10 Oct 1996 12:26:16 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Michael L Gueterman <[log in to unmask]> writes:

>Your right, this is from the DBFIND (intrinsic #404), and the error -52 means
>that the FOPEN failed to find the file.  Make sure that your not missing any
>datasets (an easy way is to go into QUERY and do a 'FO SETS' for that
>database.  If your missing any sets, you'll see the error 52 again there.  If
that
>works ok, are you utilizing Omnidex or SuperDex?  If so, then something is
>probably not setup correctly there (I've not played with either from Image/SQL,
>so I'm not sure what to look for there).

Uh, my Image manual says that error -52 for intrinsic #404 (DBFIND) is "Bad
Item"; that is, the "item" parameter is incorrect.  The manual says: "ITEM is
the name of an array containing a left-justified name of the detail data set
search item or is an integer referencing the search item number that defines the
path containing the desired chain.  The name can be up to 16 characters long.
If shorter, it must be terminated by a semicolon or a blank.  The specified
search item defines the path to which the chain belongs."

You may be thinking of FSERR 52, which is "File not found".  I believe
TurboImage error -52 on a DBFIND means that the item specified is not a search
item in the data set referenced.

Jim Phillips
[log in to unmask]

ATOM RSS1 RSS2