[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: |
Busser, James |
Subject: |
Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused |
Date: |
Mon, 31 Oct 2011 22:12:07 +0000 |
On 2011-10-31, at 2:07 PM, Karsten Hilbert 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 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?
-- Jim
- [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/30
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/30
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/31
- Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused, Busser, James, 2011/10/31