Hi Reena - and I hope Alex sees this too!
If I do a cut and paste online there is no problem, my text gets formatted properly. But with imports that's not the case.
Alex says:
---
Hmm, the import should have handled this. The `` are from the flatfile
version. A quick fix would be to go to SQL Monitor and type:
UPDATE table SET col = REPLACE(col, "``", "\n");
where table is the name of the SQL table and col is the column name that
has the `` chars in it.
---
I confirm that the import does not handle this. Testing Alex's 'Quickfix', there is no change and the linefeeds are still not converted. To be precise, in my imported file what you Reena see as apostrophes, in mine is present as hex 0B data and this is not converted into <CR>.
I hope that GT can make progress on this issue which has been dogging me for over a month!!
Hopeful
Charly
If I do a cut and paste online there is no problem, my text gets formatted properly. But with imports that's not the case.
Alex says:
---
Hmm, the import should have handled this. The `` are from the flatfile
version. A quick fix would be to go to SQL Monitor and type:
UPDATE table SET col = REPLACE(col, "``", "\n");
where table is the name of the SQL table and col is the column name that
has the `` chars in it.
---
I confirm that the import does not handle this. Testing Alex's 'Quickfix', there is no change and the linefeeds are still not converted. To be precise, in my imported file what you Reena see as apostrophes, in mine is present as hex 0B data and this is not converted into <CR>.
I hope that GT can make progress on this issue which has been dogging me for over a month!!
Hopeful
Charly