Back in the Year 2000, I used to do managed hosting in Silicon Valley. A lot of my customers were startups offering data translation services, like Commerce One... basically, you upload from database one, the site does all sorts of XML based magic, and spits out a download formatted for database two.
Unlike the average San Jose startup, these people actually had a business model and adequate technology to meet the problem... what killed them was the human factor... "Do what I mean, not what I say", and "Garbage In, Garbage Out".
What's that got to do with LANDesk? Well, I've been putting a lot of thought lately into the problem of external data integration. This is being gradually formed on the External Unmodeled Data page at http://www.droppedpackets.org, but I'm also toying around with some code. Here's sort of a hybrid between options 2 and 3 from that document... a tool that preprocesses data and injects it into LANDesk Asset Manager. Because most CRM systems that customers want to pull data from spit out CSV, I've dispensed with the XML step.
The chances of the compiled .exe being useful to anyone are about nil, unless you structure your incoming data and receiving LDAM tables per the assumptions in the program. No linking is done by the import, we're just inserting PO's and Invoices and leaving the linking to another day.
You'll want to look at the source to get anywhere. If you're not intending to write your own data import tool, don't bother downloading this.
EDIT: I fixed some bugs. It's still not useful to people who aren't writing their own tools though.
