Have you ever wondered what the dashboard symbols mean? If a picture is worth a thousand words, there’s no guessing what the unexpected appearance of a dashboard symbol is worth to drivers. Here are 63 dashboard symbols and their meanings to help you make safe driving choices.

Hi all, I am writing ascii characters to file, reading the file and updating it at intervals in my application. I am having troubles after I update the file (write) in that it becomes unreadable. I have checked the Convert EOL setting on the read text file vi and it works sometimes. Sniper assassin 5. However, I am reading and writing all the time. I have tried checking Convert EOL for the write text file vi as well.

This doesn't seem to work. Should I be writing with Convert EOL unchecked and reading with Convert EOL checked? Most of the threads in this forum indicate that Convert EOL should be unchecked. I have not seen any detailed explanations of exactly what Convert EOL means.

What does it mean? My application and text files need to be compatible for numerous Windows platforms including 2000/XP and Vista. Also, could I avoid this issue of Convert EOL by using the write and read Binary file vi's? Are they suitable for ascii characters (text)? Thanks, Battler.

Hi battler, ' I am having troubles after I update the file (write) in that it becomes unreadable' Which way 'unreadable'? Can't the file be opened for reading? Is the text screwed up? ' I am reading and writing all the time' Is there any order for read/write accesses?

Do you overwrite existing text? Do you use proper 'SetFilePosition'? Do you append to file? 'any detailed explanations of exactly what Convert EOL means' 'Convert EOL' will convert any EOL char combination to the type of EOL that is supported by the current OS 'compatible for numerous Windows platforms ' For Windows the EOL setting didn't change so far, hence uncheck 'Convert EOL'. 'could I avoid this issue of Convert EOL by using the write and read Binary file vi's? Are they suitable for ascii characters (text)?' Thanks GerdW.

I understand that since my application is only going to be deployed to Windows machines and they all use the same kind of EOL character set then I do not have to worry about any EOL conversion (i.e. It should always be switched off). The problem was that the default when you use one of these text file VIs I believe is EOL conversion turned ON. The app I was having a problem with was a conversion from a previous version of LV which had other text file VIs with EOL turned OFF. The combination of file vis with EOL ON and OFF caused the problem.