> Here is the error:
> 
> Cannot find any ??????.log file in this directory.

`elconv' is just a simple tool to convert pre 2.0 log files to the current
format. (Well, after all these confusions, dropping it from the future
releases won't be surprising -at least for me- ;) You might try some
well-known text-processing tools ie. preferably awk or perl to make the
required conversions. But I think using comma or tab as the delimiter is not
suitable due to the content of logs. If all you want is importing them to
excel/word, you should play with the delimiter options of mentioned programs
before trying a solution.

We are using elog as a small database system, today we came across a 
problem where 2 people were editing the same record and the first one to 
submit his changes were overwritten when the second person submitted his.

Is there anyway to lock a logbook record when someone has pressed EDIT, 
maybe set a flag in the logbook entry so it has to be unlocked when its 
submitted by the originator or by an administrator.

Many Thanks

Can anyone tell me the URL for the CVS download section

the link has gone from one of the main screens

Cheers

Can you tell me what the following change in CVS offers

Revision 1.99 / (download) - annotate - [select for diffs] , Fri May 2 
10:00:31 2003 UTC (6 days, 2 hours ago) by midas 
Changes since 1.98: +10 -1 lines
Diff to previous 1.98 
Added lock icon for protected logbooks


Does this relate to the request in article 309

and if so is there any flags set to enable it.

Cheers

Is there a possibility to integrate into ELOG some more features in terms 
of page formating?

Currently, the .cfg file allows you to specify only the data structure of 
the dataentry/consultation HTML page. And you only have very limited 
possibilities to change the layout of the page (basically only the order of 
attributes on the page and with the help of the .css file the font, color 
and background of the page as a whole).

What we would like to do is to :
+ apply a stylesheet class to an attribute (change the particular TD class)
+ specify the width of a textfield (sometimes it is really not necessary to 
have such a long textfield area for a 3-letter long code)
+ put an attribute on the same line as the previous one (instead of putting 
it automatically on the next line)

Therefore, in addition to the current attributes & parameters, we suggest 
the following syntax in the .cfg file:
+ parameter AttribPos which would specify the position of an attribute, 
it's lenght (for text attributes only) and the .css class to apply
+ parameters in [] are optional
AttribPos AttribName = same_line, width, [class]

Examples: 
AttribPos DateUp =  0,20, [important]   
+ Attribute "DateUp" will be put on the next line, the textfield width will 
be 20 characters and a .important class will be applied to it from the 
default (or specified) .css file.

AttribPos DateUp =  1,15,
+ this puts the DateUp attribute on the same line, width 15

We believe that these improvements would help to make the ergonomy of the 
screen better and thus facilitate the user-dataentry/consultation. 

Ive just been alerted to a bug with email notifications in Elog.

Basically if your log book contains a space then the URL that is sent in 
emails when creating tickets or updating old entries doesnt put %20 (IEs 
space) inthe URL it leaves a space hense breaking the link.

for example

Correct Way prior to 2.3.8

http://192.168.0.1:99/Provisioning%20Request/35

Broken way with new version

http://192.168.0.1:99/Provisioning Request/35
                                 ^
Link is broken at this point

My config looks like this

Email Status Assigned = $Owner@abc.co.uk
Email Status Re-Assigned = $Owner@abc.co.uk
Email Status Completed = $Requester@abc.co.uk
Email "Send Update Email" Yes = $Requester@abc.co.uk
Use Email Subject = A Provisioning Ticket has been assigned to you or 
completed
Use Email From = NetworkTeam@abc.co.uk

we develop some improvement to elog and modify the C source
to adapt some internal improvement.

1. shellonsubmit command : give the possibility to execute external program
from elog by sending specific parameter (user/logbook/message ID)

2. elog log file in xml format : give a better view on what happens with 
users see attachments easy to push the files to excel or sql database.

3. synchronisation to mySql or SQL server through perl routine and the 
shellonsubmit command
this will push any new/edit/delete command in sql server so we keep a full 
historic off all transaction in ELOG

4. sms gateway : from elog entry we send sms message throught internet 
gateway (perl routine)

If somebody has good experience in C and Perl I suggest to contact me to 
improve this wonderfull product
Thank Stephan

other projet : 
we use a logbook from our external phone call

from our telephone connected to RS232 and/or TAPI interface we keep the 
phone number and try to find the name from sql server : if found 
we want to push an automatic entry in elog and fill specific field like 
name/contact/last phone call....


I will ask to Stephan Ritt what's the best way to include our routine in 
his standard source ?

could we create a specific logbook for the wishlist
in elog/contribution may be some parameters for the actual status of the 
project ? 

SQL : 
for our sql link we have a probleme as elog re use id when deleted
we must generate an unique ID for each elog CREATE 
and a version# field automaticly incremented after each update.
This must be implemented in ELOG source.

Seems a stack problem.  I don't have an OS X box to validate my guess.  I've
made a Google search with the keywords: EXC_BAD_ACCESS stack "os x"

Perhaps the following reply [1] might help...

  How big are they? You're probably running into the default stack size 
  limit, which is 512 KB. Try `unlimit stacksize` in your shell before 
  running, which will give you 65536 KB per stack.

[1] http://zerowing.idsoftware.com/archives/gtkrad-macos/2003-January/000453.html