Solved

different results when exporting to .csv and .chr files

Posted on 2004-09-27
7
920 Views
Last Modified: 2008-01-09
We use crystal to export our invoices to Sage.
With Crystal 7, I could use a .chr format, or a .csv.
The .chr  format worked fine.
However, since upgrading to Crystal 10, the .chr format is no longer available, and sage is reporting errors, saying there is no line feed, and one field per line is not being updated.

The only difference I can find is that the .chr format has an extra comma on some lines, but not all.

Does anyone know what the difference is in the file formatting?
0
Comment
Question by:wyliecoyoteuk
  • 3
  • 3
7 Comments
 
LVL 42

Expert Comment

by:frodoman
ID: 12168426
AFAIK the only difference between .chr and .csv is the character used to delineate fields and records.  CSV uses a comma to split the fields and there's no delineation between records - just a continuous series of comma separated fields.  CHR can be defined to use virtually any character to separate fields and a different (or the same) character to separate records.

If your application is expecting .chr format then you'll be missing a character (sounds like a comma in your case) at the end of each record and you can expect that it won't work.  You would have to manually (or write an application to do it) insert a character at the end of each record in order to make the import work as expected.

Further complication - since CR10 is unicode compliant and CR7 wasn't, it's also quite possible that the new export will contain double-byte characters where the old one may have been single-byte.  Even if you resolve the format issue, this may be yet another problem that you're going to have to deal with.

You may want to check with the Sage folks and see if they have an updated import driver that will allow you to use CR10 .csv files.

frodoman
0
 
LVL 21

Author Comment

by:wyliecoyoteuk
ID: 12171628
That`s what I thought, but crystal produces different text files, even when set to use a comma as the delimiter.
the extra comma appears in the middle of some lines, but not others.
The problem is complicated by the fact that the report was written for our old database(access backend), by our old provider, and we now have moved to a new database backend (IBM universe). the new provider has produced an export routine for us, but it suffers from the same problem.
The Sage people just say that it is a problem with the export routine, and disavow all knowledge:(

as an example:

12345,300404,300504,30.95,314004,,,,,,,,10.2,9

these are :
invoice number
date raised
date due(30 days from date raised)
cost
cost
nominal code
empty fields(varies depending on number of items per invoice)
tax
number9 ( i assume this is an endof line code)

The extra comma appears in the empty field sequence, but not on all lines, and not in any easily discernable pattern.

The error caused is that the due date is incorrect.

Thanks for your input.
Maybe I should move this to the sage forum.
0
 
LVL 42

Expert Comment

by:frodoman
ID: 12172630
Well obviously I don't know your data so I can't speak to extra commas, etc.  But unfortunately as I've said your options are limited.  Unless you can go back to CR7, then you're going to have to either alter the export after Crystal has dumped it or alter the way Sage reads it (unlikely of course).

Frankly I'd consider going back to CR7 if that's remotely an option.  The biggest problem there is that it isn't supported on more recent versions of Windows so you're stuck in a non-upgradeable situation if you do that.

frodoman
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
LVL 21

Author Comment

by:wyliecoyoteuk
ID: 12351597
Finally solved it, (though the extra comma still remains a mystery).
Turns out that when our support people "upgraded" sage, they trashed the import settings.....................................
This unfortunately coincided with the CR10 upgrade, and when I finally managed to get a machine I could install CR7 on and try the old report, it failed too....
(CR7  16 bit still works fine on XP, by the way)

0
 
LVL 42

Expert Comment

by:frodoman
ID: 12351680
Aha - sounds like it's time to kick the support people! ;-)
0
 
LVL 21

Author Comment

by:wyliecoyoteuk
ID: 12352160
yup:)
0
 

Accepted Solution

by:
ee_ai_construct earned 0 total points
ID: 12352546
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Crystal Reports: 5 Tests for Top Performance It is complete, your masterpiece report.  Not only does it meet your customer’s expectations, it blows them out the water, all they want is beautifully summarised and displayed in a myriad of ways. …
Hot fix for .Net Crystal Reports 10.2.3600.0 to fix problems with sub reports running on 64 bit operating systems ISSUE: Reports which contain subreports fail with error "Missing Parameter Value" DEPLOYMENT SERVER OS: Windows 2008 with 64 bi…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

829 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question