Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!ncar!gatech!ukma!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/AA)
Newsgroups: comp.databases
Subject: Re: ACCELL problems
Message-ID: <1991Apr29.170512.14093@NCoast.ORG>
Date: 29 Apr 91 17:05:12 GMT
References: <1991Apr25.185015.1978@hrc.uucp>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/AA)
Followup-To: comp.databases
Organization: North Coast Public Access Un*x (ncoast)
Lines: 22

As quoted from <1991Apr25.185015.1978@hrc.uucp> by dan@hrc.uucp (Dan Troxel):
+---------------
| existed which would cause ACCELL to barf half-way through creating the
| application, but this is not the case.  All I can figure is that unify.db is 
| corrupt.
+---------------

Not unify.db, but aclenv.db.  Exit Accell, remove shared memory, remove
aclenv.db, and re-enter adev.  A new aclenv.db will be created.  Then you can
re-register your existing applications.

I've seen this happen when sequence numbers get out of step for some reason.
Deleting a lot of forms may exacerbate it.

Personally, I do my development from the shell instead....

++Brandon
-- 
Me: Brandon S. Allbery			  Ham: KB8JRR/AA on 10m,2m,220,440,1.2
Internet: allbery@NCoast.ORG		       (restricted HF at present)
Delphi: ALLBERY				 AMPR: kb8jrr.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery       KB8JRR @ WA8BXN.OH