Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ucdavis!csusac!unify!mef
From: mef@Unify.Com (Marvin Fenner (att))
Newsgroups: comp.databases
Subject: Re: ACCELL under SCO - prob saving screens
Message-ID: <3z0snzw@Unify.Com>
Date: 26 May 91 18:52:17 GMT
References: <33138@usc>
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 40

In article <33138@usc> rpinder@phad.hsc.usc.edu (Rich Pinder) writes:
>Unify Accell, v. 1.2.0.8.0, running on SCO 3.2 rel 2 on a NCR 486.
>
>I have the following confusing problem.  When using the Development
>environment, accessed from the accell script I am having a problem
>saving a form that I created.  When logged in under my own account, I
>get this error when trying to save (either F9 or esc-a-u), but when I
>use another account just set up (using exact copies of my own
>.profile and .kshrc files) I can save the form just fine.  Also
>strange, if I (under my own account) use the adev command to enter
>the development environment, I !can! save the thing.  The drawback of
>continuing this workaround is that when using the environment via
>adev, I get garbage 'residue' on the screen (after going to a
>previous form) and also don't get any of the graphic drawing
>characters (ie in drawing borders).  

Rich,

The reason you are seeing screen residue is that 'accell' and 'adev'
are not using the same logic for determinig which termcap to use. I
would guess that 'accell', by default, is using the termcap provided in
your release ($UNIFY/termcap), whereas 'adev' uses /etc/termcap.  Note
that 'accell' exports $TERMCAP, which is then picked up by 'adev' when
run via 'accell'. We have corrected this feature in later releases.
Perhaps the easiest fix for you is to explicitely set $TERMCAP to
$UNIFY/termcap.

Some thoughts about your other problem: 'accell' doesn't alter $ACLENV
(the path to your application files), but it does set $DBPATH. 'adev'
sets $ACLENV relative to $DBPATH (if $ACLENV is unset). Perhaps your
$DBPATH setting is different when running 'adev' vs. 'accell'. One
thing to try is to invoke the Development Environment from both 'adev'
and 'accell', push a shell (via the O.S. menu selection), and determine
whether or not you end up in the same directory.


Marvin E. Fenner   | My disclaimer is available for public viewing
Unify Corporation  | between the hours of 8:30am and 5:00pm PST, ...
Sacramento, CA 95834
mef@unify.Com