Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exporting to Ascii file with Crystal 8.5 on Windows XP 1

Status
Not open for further replies.

BnkMaggie

MIS
Mar 24, 2003
4
US
Running Crystal 8.5 on Windows XP
We have a report that exports data to an ascii file. It is then picked up by back office software. It works fine under Windows 98, but the generates errors if run from Windows XP when I import it into the back office product.
Everything is the same, just the operating platform changed.
Any suggestions? Thanks ever so much.
 
Hi, What errors? It is hard to guess.

I suspect the increased security enforced by XP may be at the root, but without knowing the error, it is just a shot in the dark.( XP Home or XP Pro?)

[profile]
 
The back office software begins to import the file but then
gives the error message Currency not on File, Import Aborted. OS is XP Pro. I'm thinking the data isn't in the columns it expects. Specs call for a field to start in postion 1, next field to start in position 21...and so on. the Currency field is the 4th data element in. So the issue is how can I line this up? Lining up the columns against another file from another source being loaded into the same back office software hasn't helped.
 
In spite of that ( certifying for XP takes a while), we have several developers using CR ( 8.5 and 9) with XP Pro with absolutely no issues whatsoever...
What errors are you getting???

[profile]
 
The software importing the file doesn't give us an error message. It isn't an abend. The file is opened but when it reaches the 4th item it says the information is invalid and then all you can do is acknowledge that message and exit.
.
The file has an account number, a company code and a region code before it gets to the currency code and says the code is invalid. All the prior fields are also in tables and also validated. Could the issue be trying to read count columns ie field starts at position 21 and ends at position 35 which is produced in scalable fonts?
 
Hi, With positional data and variable fonts ( as well as trim issues), there is always the chance that the data fields are being misread..
Can you view the output in a text editor and check the locations of each field's start and end?
Conversly, can the back office software read any other format..Like comma delimited or some other delimited format? That will avoid the positional issue.

[profile]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top