Menu

Tree [r1] /
 History

HTTPS access


File Date Author Commit
 bin 2009-06-22 fiege [r1] Initial-Release
 obj 2009-06-22 fiege [r1] Initial-Release
 AssemblyInfo.cs 2009-06-22 fiege [r1] Initial-Release
 Program.cs 2009-06-22 fiege [r1] Initial-Release
 Readme.txt 2009-06-22 fiege [r1] Initial-Release
 Tools.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_2HTML.csproj 2009-06-22 fiege [r1] Initial-Release
 VDA4905_2HTML.sln 2009-06-22 fiege [r1] Initial-Release
 VDA4905_511.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_512.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_513.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_514.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_515.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_517.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_518.cs 2009-06-22 fiege [r1] Initial-Release
 VDA4905_519.cs 2009-06-22 fiege [r1] Initial-Release
 gpl.txt 2009-06-22 fiege [r1] Initial-Release

Read Me

VDA4905_2HTML 


So you are in the need to handle VDA documents......

You have different options

You could buy a commercial solution.....
[A good option if you have enough money at your hand.]

You could extend your ERP to have the ability to handle those documents.....
[An even better option, but it needs more money]

But if you receive not so frequently this VDA4905 schedules all of this is a little oversized.



Q:So what about this VDA4905_2HTML ?
A:An easy to use tool to convert a VDA4905 delivery schedule document in a human readable format.


Q:How do I use it ?
A:Just type VDA4905_2HTML on the command promt and add the VDA4905 message as a parameter
The output will be the HTML documet or an error message in case soemthing went wrong.
You could use the following command line switches:


-IF=InputFile 	-> Reads the VDA4905 froma text file maybe could be encoded by the EBD dictionary
-OF=OutputFile 	->  Write HTML to a file instead of printing it to the command line
-EBCDIC 	-> Turns on the EBCDIC to ASC conversion before handling the input file (Only available in file mode)
-Info 		-> Version info output


Q:Can I run it on Linux/Mono ?
A:It runs but it throws an exception about a missing code page on my Fedora 8 machine.
This codepage is needed to do the EBCDIC conversion and it seems that the Mono version I use doesn't suports it.
If you are in need run it on Linux and you don't need the EBCDIC support, open the Program.cs file 
and change the followin line:

System.Text.Encoding encoding = System.Text.Encoding.GetEncoding(37);

to

System.Text.Encoding encoding = System.Text.Encoding.Default;

Compile it and it should run on Linux/Mono too. Unfortunately I am short in time currently, so I can't test it now.

Q:Can I use the conversion mechanism in my own code ?
Sure, just takte the source and add it to your project.
If you are using .NET you can use Reflections to call the doConversion method and have the conversion logic in less than 10 lines of code.

Q:Can I attach the funcion to my ERP or DMS ?
A:Sure, use the reflections mechanism.

Q:Where can I find detailed informations about this VDA document specifications ?
A:Go the VDA's webpage (vda.de) and use the local search engine.


That's it so far,

This tool was programmed using SharpDevelop 2.2.1 Build 2648 and is intended to be usefuel.
It comes with absolutely no warrenty and is licensed under the GPL V2 or later.
The license text is attached in a seperate text file.
If you find any error file it on Sourceforge or drop me a message to pommes@teleos-web.de .

Take care !








Changelog:
20090621 V1.00 initial release