I'm looking up the project now. You have to add a reference in the dotnet project to a dll supplied by Intuit.... Interop.QBXMLxxx. Once you have the reference, below is the sample code. I can't locate the doc that was part of the SDK download from Intuit. But it basically listed all the XML calls you could make along with their parameters. This is to download the inventory file:

            //step2: create the qbXML request
            XmlDocument inputXMLDoc = new XmlDocument();
            inputXMLDoc.AppendChild(inputXMLDoc.CreateXmlDeclaration("1.0", null, null));
            inputXMLDoc.AppendChild(inputXMLDoc.CreateProcessingInstruction("qbxml", "version=\"2.0\""));
            XmlElement qbXML = inputXMLDoc.CreateElement("QBXML");
            inputXMLDoc.AppendChild(qbXML);
            XmlElement qbXMLMsgsRq = inputXMLDoc.CreateElement("QBXMLMsgsRq");
            qbXML.AppendChild(qbXMLMsgsRq);
            qbXMLMsgsRq.SetAttribute("onError", "stopOnError");
            XmlElement itemQryRq = inputXMLDoc.CreateElement("ItemInventoryQueryRq");
            qbXMLMsgsRq.AppendChild(itemQryRq);

            string input = inputXMLDoc.OuterXml;
            //step3: do the qbXMLRP request
            RequestProcessor2 rp = null;
            string ticket = null;
            string response = null;
            try
            {
                rp = new RequestProcessor2();
                rp.OpenConnection("", "IDN Inventory Item Request");
                ticket = rp.BeginSession("", QBFileMode.qbFileOpenDoNotCare);
                response = rp.ProcessRequest(ticket, input);

            }

>I'd be curious to here the name of the control you were using. That does sound similar, but the catch was that the samples would be snippets showing how to add a particular piece of data, but to get to that point, lots of other ducks had to be lined up first. For example, if you were going to reference ITEMS on a STATEMENT, the item had to be there of course and you couldnt simply try to add it again or it would error due to duplicate names. So, you have to search for it and add if missing. (And the 'search' features were lacking.) I had debated about pulling all that QB 'lookup' stuff over and saving it for the duration of the users VFP session. Granted that could be a lot of data and it could become stale too.
>
>>I worked on something with dotnet and QB for a bit before the project got dropped. It seemed pretty easy to do without 3rd party tools. I don't remember the specifics but I think it was just a matter of calling a QB com component and telling it to spit out some XML, or sending the component XML.
>>
>>If I recall correctly, it was just a matter of starting with one of the examples. Then there was a document that listed all the calls you could perform, so you just had to find the right one.
>>
>>>I have used this 3rd party activex control for QB QBXML integration:
>>>
>>>http://www.nsoftware.com/ibiz/quickbooks/default.aspx
>>>
>>>But its been a start/stop effort so far, although i do like the control so far. Its pretty slick to watch the data appear in your QB session as you push data from VFP. The biggest issue i've found is adding/updating QB in the right sequence, so that the validations are met. That means populating the QB data (ITEMS, CLASSES, COA CODES, CUSTOMER:JOBS, VENDORS) in the correct order and validating the existance of this data before creating/updating STATEMENTS and INVOICES and applying payments.
>>>
>>>I was hoping to replicate what i do when updating MSOutlook from fox and that is to store a PK value on an Outlook contact record (in a rarely used field) and simply search for that value in order to determine if an add or an update is needed. But have not found a a means of doing the same w/ QB. The version of the control i have does not support the creation of or the searching of user-defined QB fields (that may have changed though).
>>>
>>>>Are there anyone in here that have "integrated" with QuickBooks in their application?
>>>>I am starting to look into exporting to QuickBooks and I am curretly gathering information and trying to get the "big picture" overview.
>>>>Any links, book references or comments (on the topic) would be welcome.
>>>>
>>>>Thanks,
>>>>Einar