I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it. 

 Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet.   They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients".  So you see why I find it amusing.  I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin).  First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy.   Please let us know.

I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer. 

Hi,

I am using the # character to generate automatically incrementing numbers for new messages.

My issue is that # is evaluated when you hit "New" but E-log is only aware of the new value being used when you hit "Submit".

So, two E-logs can have the same value substituted for # if two E-logs are being edited in parallel.

Maybe someone has a solution to this ?

Soren Poulsen

Hi,

Here is what happens (I think) if E-log encounters a full file system where it keeps the user authorization file:

1. When a user connects, E-log will make a backup of the file. The backup will be corrupt since the file system is full.

2. E-log will modify the contents of the original file, and write it back. The file will be corrupt since the file system is full.

3. Now, both the backup and the normal file are corrupt and you cannot log on, until someone cleans up the file system and restores a valid copy of the file.

Would it be possible to fix this ? Like abort if step 1 is not successful. And restore the backup file if step 2 is not successful.

Thanks a lot for you help 

Soren

Hi,

I use the following attribute definition:

Options <attribute> = <list> 

However, I am being limited by the list length limit of 100. I have 103 items, but I only see 100.

Could the limit be extended (to 200 for instance) ?

Thanks a lot for your help

Soren