Exporting to ASCII from Crystal-spaces at first field

[traigo]

I am exporting a single line report to an ascii database file for email. I keep getting a leading space in the export file. I have tried using the trim() function on the first field, but there are no leading spaces. I have placed the field at the far left and set all margins to 0. I've been told this is a bug in crystal exporting. Is there a fix for this yet?

There are 10 types of people in the world, those that understand binary, and those that don't.

 

[synapsevampire]

Try including your version of Crystal, as with any software, the version is critical.

Also Crystal doen't have an ASCII export, so try using the actual Crystal terms when posting questions.

You're probably referrring to the TEXT export, which is a known problem with a fix available:

http://support.businessobjects.com/library/kbase/articles/c2009189.asp

-k

 

[traigo]

CR: 8.5.0.217

I am not exporting from crystal. The report was written in crystal, but there is DOS-based clipper program that does the actual exporting using the "TEXT" export. If I knew what the actual crystal terms were before posting, I would already know the answer to my problem. It would have taken a lot less effort just to post the link.

There are 10 types of people in the world, those that understand binary, and those that don't.

 

[Turkbear]

traigo,
There are also 2 kinds of people in the world,
those who appreciate others' efforts to help them, and those who don't.

 

[synapsevampire]

Thanks, Turk.

I never know how to respond to such things.

Note the 1st post says Crystal exporting, the 2nd says Clipper does the exporting.

Probably just frustrated and lashing out.

Understandable when dealing with Clipper and an old version of Crystal.

-k

 

[traigo]

I am not saying I don't welcome the help. I really do, but when frustrated with these things, such sarcastic remarks just make it worse. I really appreciate the help, but not the comments. Anyway, I tried the hotfix but it still does the same. As far as the version, I am limited to what my company is willing to purchase. I have CR9 at my house. I miss some of the features here. For liability purposes, I cannot bring mine here. Also, all our customer, the ones who get my reports after writing them, only have 8.5, so it wouldn't do much good to be on 10 if they can't work with the reports.

There are 10 types of people in the world, those that understand binary, and those that don't.

 

[synapsevampire]

Many people who post here don't realize that the version of their software matters, and don't understand that their terms mean different things in different contexts.

You did know the TRIM function, so I figured you weren't a beginner, but it usually doesn't hurt to remind people to be thorough.

Note that the patch I offered was CR version dependent, it was for CR 8.0, not 8.5, no surprise that it didn't work for you, the problem probably lies elsewhere. You should have read the link carefully.

So you feel that I should have known that you were in Clipper, known your version of Crystal, and that you were insulated from knowing about the export types in CR from your first post? Therefore I was being sarcastic?

Abyway...

You can always export using xBase:

copy to <filename> type SDF (or whatever)

Yep, used to code xBase for many years.

OK, end of comments/communications, good luck.

-k