Exporting Report to ASCII file using PDISK (AREV Specific)
At 19 MAY 2000 05:46:19AM Pete wrote:
I'm currently exporting reports from our AREV 3.12 application sitting on a NT server into ASCII text files. I have written a batch reporting module to re-direct reports to text files using the PDISK command instead of to the printer. This batch process is run on a PC running NT. These reports (text files) will next get uploaded into a reporting database. Each report has to be patterned before it can be uploaded.
Some of the reports were found to be of ANSI format.
Q: I thought the PDISK command always generates an ASCII text file. What would cause AREV to generate ANSI text file? Could it be a due to the PC environment?
At 19 MAY 2000 07:05AM Steve Smith wrote:
By ANSI I'm assuming you have imbedded escape sequences in the report, eg. HEX 1B / char(27) followed by some other characters.
This is probably formatting for the printer selected.
Steve
At 19 MAY 2000 11:00AM Larry Wilson - TARDIS Systems, Inc. wrote:
If you want just a straight ASCII report, define a new printer to use and remove all formatting commands from the printer definition. This should result in no characters LT CHAR(33) or GT CHAR(127) being inserted.
An option is to write a piece of cleaner software that will scan the DOS file and remove those commands for you. I have such a piece of software that I'll post on my website by Monday (got a bit of cleaning up to do for public consumption).
(if you see a floating chat icon, it means I'm paging you to chat)
At 19 MAY 2000 12:22PM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Oh that's what that meant- sorry!
World Leaders in all things RevSoft
At 19 MAY 2000 05:12PM Oystein Reigem wrote:
Pete,
Don't know why I reply because I haven't used Arev for years, haven't got it installed, and probably cannot help you. (So why did I read your posting at all?) But do you with ANSI vs ASCII mean the Windows text character set vs MS-DOS text? (That's how I use the two terms.) They are equal in the lower part but different in the upper one. So are you really talking about 8-bit characters that come out wrong?
- Oystein -
At 21 MAY 2000 02:38AM Steve Smith wrote:
I'd probably retain the ubiquitous char(12)=ASCII formfeed
Steve
At 21 MAY 2000 02:40AM Eric Emu wrote:
]] This should result in no characters LT CHAR(33) or GT ]] CHAR(127) being inserted.
I'd definitely remove char(13) and char(10) - these are nothing but trouble.
Eric