We just had a strange issue that our webfocus system can't read some text data files that used to be working properly.

After some digging I found the cause is the linebreak characters. When the linebreak is {LF}{CR} (0D 0A) it works but when the linebreak is {CR} only webfocus can't read it.

Has anyone had this issue?


Update: Let user know make sure the format is correct before sending the file to us...

This message has been edited. Last edited by: bug,

When you say WebFOCUS can't read it, do you mean your Synonym can't read it?

Files with only {CR} is usually a unix/linux behavior, however there are some lazy window developers that do this as well.

Is the file all {CR} or all {LF}{CR} or is it mixed as some lines ending in {LF}{CR} and some lines ending with just {CR}?

All good and bad files are from the same source. When files are bad, all linebreaks are {CR} only. Webfocus will return 0 lines.

My guess is the person who generated this file are using both Mac and PC.

Is there a way to specify both sets of linebreaks in webfocus synonyms?

I would suggest adding calls to your fex to clean up the files.

Say replace all CRLF's with CR's, then again from CR to CRLF, so the whole files is the same.

This can be done using calls to utilities like SED.

Bug,

If your file has fixed length records, then you can define the {CR} in the MASTER file and WF will read correctly.