Export Properties to XML using VBA

[michael_berger]

Hi i'm looking for a way to export some iproperties (Custom an Standard) via VBA to an formatted xml.

the xml should look like this: 

    <PPSImport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <Parts>
            <Part PartNo="Vault-Name">
                <PartNoExt></PartNoExt>
                <Description></Description>
                <CADFilename></CADFilename>
                <DrawingNo></DrawingNo>
                <Note></Note>
                <IsAutoRemoveable>0</IsAutoRemoveable>
                <FavoriteBendToolList></FavoriteBendToolList>
                <BendAllowanceType></BendAllowanceType>
                <KFactor></KFactor>
                <BasicMaterial></BasicMaterial>
                <Material></Material>
                <MaterialDescription></MaterialDescription>
                <MaterialThickness></MaterialThickness>
                <Length></Length>
                <Width></Width>
                <UnitOfDimension></UnitOfDimension>
                <CustomerNo></CustomerNo>
                <CustomerName></CustomerName>
            </Part>
        </Parts>
    </PPSImport>

can someone help me? i don't have many experience in vba so maybe someone can give me some code snipplets?

thanks.

[MechMachineMan]

The google machine is fantastic.

https://social.msdn.microsoft.com/Forums/en-US/a1af3588-fe8f-492f-88e9-dd72fca624bf/write-xml-entry-...

[michael_berger]

hi
thanks, it must be a very new invention this „google“...
well i found this
post too but i‘m very new in vba so i‘m not sure if it works direct from inventor to xml i dont want to export tonexcel and then to xml, i want direct from inventor to xml....

[dgorsman]

Are you familiar with the MSXML DOM?

[MechMachineMan]

Half of programming is trying this out. The other half is researching.

As long as you properly import objects, add references, and wrap things in the proper Sub Main(), in the inventor rule environment, things run just like they do in VB.net.

If you were to have done any reading about the topic, you would know the rule environment is actually a vb.net environment. And you would also know that VBA and VB.net are VERY, VERY SIMILAR aside from some syntax and the occasional availability of objects.

This being said, if you take the code from the previous link, and paste it into the iLogic environment, and have the capability to read the plain English in the error trace, and google said error lines, you should be able to solve this problem without too much trouble. And you'll learn something, so that's great too!