Error Message B16 on ASCII Export AREV ver 2.0 (AREV Specific)
At 22 FEB 1999 12:52:44PM Lynn Jess wrote:
B16 error message on ASCII Export AREV ver 2.0 when attempting to test export a few fields from file of 3000 records. Have re-installed AREV program (starting with ver 1.0, 1.1, then 2.0 upgrade) in case something had been stepped on.
Similar test on tutor file was successful. Volume/file appear attached correctly. Apparently, I have something set up wrong but do not know where to investigate. Any suggestions appreciated.
At 22 FEB 1999 01:04PM [email protected] onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Ltd[/url] wrote:
B16 is a non-numeric when numeric required zero used. Possibly a formula bug?
World Leaders in all things RevSoft
At 23 FEB 1999 06:59PM L Jess wrote:
Andrew, thank you for your input. I tried the dBase export window and it was successful. Have reinstalled the Adv Rev program again, and the ASCII export window still delivers the same B16 message. Attempted to create export statement in TCL, but that only leads back to the process defined at the export window.
Did explore the Design-Popup- for Import/Export. Found the input from Tools-Export-ASCII were in wrong fields, but the input from the dBase export were also in the wrong fields (such as, Revelation file name selected in Export window showed up in Design-Popup where Row number should display. Since the dBase export worked properly, this popup exploration apparently did not prove anything.
If the ASCII export file in our volume is corrupted, how does one correct it? Appreciate any help or thought processes.
At 24 FEB 1999 03:36AM [email protected] onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Ltd[/url] wrote:
So you are saying that the same export with exactly the same columns done to dBase works, but done to ASCII B16s? That blows away the dodgy formula theory. Can you screen print the export window as you have defiend it? What are you using for column delimiters, 44 or 9? What about record, 13,10?
World Leaders in all things RevSoft
At 24 FEB 1999 05:57PM L Jess wrote:
Andrew, again, THANK YOU. Your response triggered some thought processes.
Since we are exporting general text and scientific information relative to advanced composite materials, we imported with delimiters such as 126, 94. I am also looking at ASCII compatibility to using odd symbols such as 247, 240. When used in MULTIPLES, these do not normally appear in our records and helps ease import/export go quite smoothly. I mistakenly thought I had read a help screen which defined that delimiters could be used in multiples (two or three) separated by commas.
I tested with single delimiters, and the ASCII worked with 3000 records. Since the dBase export sets its own, I did not interfere with its function.
Our next export test is with 30,000 records. AMV's appear to be the next topic to understand before attacking that project. I see several articles already posted on this site to review before starting.
Again, we extend our gratitude to you. Also to Revelation for the ability to use this medium.
Lynn Jess
At 07 MAR 2000 09:57PM Chris Leenhouts wrote:
There is a new utility called xPort at http://exorsys.com/revelation.htm which resolves all the technical and conceptual problems asssociated with Revelation database exports.