The Carriage Return/Line Feed character that may be embedded in a field by the user, or as a FM text calculation are not represented "as intended" when FM data is "pushed" to a SQL server. In examining the "pushed" data using Ms Access, all the original CR/LFs are represented by "boxes", and no CR/LF actually occurs, so the text is a continuous string. This occurs whether developed on Macs or Windows and whether the client is on a Mac or Windows box.

Does the solution to this problem lie entirely on the SQL side? In other words, does the IT guy the runs the SQL server have to invent his own parser/translater in order to represent the data correctly to their users? Or is their a way to do it on the FM side (without creating an intermediate exported text file)?

Any help would be appreciated,

John Roths

Texas A&M Univ.

[email protected]

Well it is really just an issue of replacing the character. This can either be done on the SQL backend or on the Filemaker end. Grab the proper SQL Server and store it in the clipboard, then go into Filemaker and make calculated versions of the fields that this problem is occuring in and use the following calculation in them: Substitute ( FieldName, "

This previous calculation tip is also very useful, if you have to store field in JavaScript variable.

Obviously the JS is interpreting the "