Re: Create past Elog entry., posted by David Pilgram on Tue Apr 3 09:39:07 2018
|
Hi Michael,
Elog purists, look away now.
There is an "official" way to do this, which is to have fields for entry date (so can be in the past), but the yymmdda.log file will |
|
Re: Logfile not registering entry numbers?, posted by David Pilgram on Mon Oct 29 14:26:28 2018
|
As a regular elog (ab)user, I have seen this behaviour from time to time. So far as I recall, the cause actually is that a normal entry is looking
for the entry in the "Reply to" field of the normal entry in the yymmdda.log file. When that entry does not exist, then I see a duplicate
line of an entry with entry "#0", in emboldened black type. I did have a screenshot, but cannot find it for now. |
|
Re: Unwanted double entries eg. double clicking submit button, posted by David Pilgram on Wed Feb 13 10:58:37 2019
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
Finn |
|
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
|
Re: Windows Server 2012 - moving logs, posted by David Pilgram on Thu May 16 21:49:06 2019
|
Hi Lesley,
Perhaps I can restate Stefan's comment. The data structure of an elog entry, or indeed the structure of daily file(s) for any particular
logbook has not changed between v2 and v3. What has changed is the directory structure. A set of sub-directories (named by calendar years) |
|
Re: Record ID corruption, posted by David Pilgram on Sun May 3 18:05:32 2020
|
Hi,
I've had problems in the past due to a dodgy pointer creating branches despite a "No branches" in the configuration file.
It would be very interesting to see what the 200428a.log file looks like with these entries: in the screenshot they appear to be shown in time order, but |
|
Re: Record ID corruption, posted by David Pilgram on Mon May 4 14:55:53 2020
|
Hi Frank,
There are two interesting points about the log file.
1. Entry 5658 is timestamped later than 5659, but is earlier in the entry list. It also is "In Reply to" 5659. despite |
|
Re: Record ID corruption, posted by David Pilgram on Sat May 23 16:15:38 2020
|
Hi Frank,
Good bit of detective work. To me it suggests that something as yet undetermined occurs, that, when the 57th reply happens, causes the
issue. If that "something" hasn't happened, all is well. Apart from Heinz varieties (not true, in fact), 57 isn't an obvious |