Modification of ONIX XML conversion program
$30-250 USD
Paiement à la livraison
This project involves the modification of an existing ONIX XML to MS Access conversion program that was developed in Visual Studio 2003. Two modifications are requred resulting in one program giving two output options. The modifications are:
1. An option to process all the ONIX xml files in a directory (to be chosen at run-time). This will not be the directory where the program is located. The program will put the results in the Access database which is currently used for this purpose. Currently the program lets user select one ONIX XML file for processing - this option should still be available.
2. An option in the program that outputs a subset of the data to a flat tab delimited file instead of the Access database.
The first modification is self explanatory.
The second modification requires certain XML data from the ONIX file to be linked with data in a discount table via a discount codes field. The fields (including from the discount table) to be output to the flat file should be selectable at run-time via a dialog box. The flat-file should be TAB delimited. The discounts table will be held in a TAB delimited text file that is selectable at run-time.
The project requires the delivery of the executable program for Windows XP and the source code which will be the sole property of Keurbooms Ltd.
Nº du projet : #504035
À propos du projet
Décerné à:
11 freelances font une offre moyenne de 145 $ pour ce travail
Expert Computer engineer, having Experience in XML, XSLT, XMLSchema , Can Start Work On Immediately effect.
I am pretty confident i can do the job very well as i have done the similar job, parsing and converting huge onix xml into csv file. please see my completed projects for details. thanks and best of luck
GET THE LOCAL ADVANTAGE!!! I am a US based consultant with over 12 years of exp in MS Technologies, majority of which is in .NET. You'll get telephonic support during and after the project.
I would be happy to bid on this work. You mentioned Visual Studio 2003 ... I am ready to go with Visual Studio 2008, which means that my solution would require a different version of the .NET Framework runtime. I will Plus