[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* t

From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused
Date: Mon, 31 Oct 2011 23:16:09 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Oct 31, 2011 at 10:12:07PM +0000, Jim Busser wrote:

> > GNUmed cannot find the configured default encounter type. In
> > that case it used the encounter type with PK = 0. However,
> > that's not available in your system either and thus it fails.
> > 
> > I now changed GNUmed to use the first one that's actually
> > available if the configured one does not exist.
> Your most recent advice (set the default encounter type to one that exists) 
> solved my problem!

I know.

> I had trouble to pinpoint (within the log file) the basis
> for the error… previously I would visually scan or search
> within the log for 'ERROR' however that simply identifies a
> number of conditions (optional functionalities?) without
> which GNUmed can and does still function 'normally'.
> It now seems that, when searching a log (at least, one
> which triggered an unhandled exception) the keyword
>       Traceback
> will often identify the problem?

None of the above identify the problem. They identify
evidence. Think of it as CSI.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]