I think your main course of action should be to determine how the program opens the database and with what password and decompile the database to create a schema (adager or bradmark) and make sure that something didn't change. Image typically doesn't lie so if you're getting -23, then that likely is the issue. Repeating the mantra "nothing changed" makes people like me nervous and suspicious. :)

Once you've shown that the obvious error is NOT true then looking for the exotic makes sense.

Neil

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of Eddie Hopper
Sent: April-04-12 12:52 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Image: Image error, what am I missnig?

Thanks for checking in on things, we still have an issues hidden somewhere.  And to clarify, this particular database was not set to read only, it was actually extraneous to the changes.  It is used as an intermediary between external users and our production data.  A request comes in and the requesting user information is written into this database, then the pertinent unfo is used pull data back from the production data and then transfer back to the requestor.

So to the best of my knowledge, there were no direct changes to this database/sets/passwords, nor to the user/group/account access or capabilities.  So figuring out why the failure to open mode 1 is the mystery.

A brief update, Suprtool was used interactively and in a quick job, usnig the same user.account and group.  No issues opening, writing a record, then deleting the record.  The only caveat I have, the expected password is truly used to open the DB.

Maybe banging my head on the racks will jar something loose.
eddie

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

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