>We have a VFP application that we wrote to work with QuickBooks Pro via its transaction import utility. Basically the A/P is generated by the VFP app and then the invoice data is emported to QB's IIF format for import.
>
>The problem is that alot of the fields that QB specifies in thier import format don't actully work. QB tech support simply states that they don't support the import function. Nice approach. They should either make it work or exclude it from the software.
>
>We use Quick Books Pro 2003. We really have no reason to upgrade to 2005 except of course if they have fixed the import which I doubt.
>
>Quick Books has a developers program that is used to integrate programs into thiers. Has anyone used it? Will my FoxPro knowledge be enough for me to use it or is it based in another language.
>
>Thanks,
>Larry Morelli

I used the IIF for imports for a couple of years without problems. Build the file as a CSV in Excel first. Change the extension to IIF and get it to work that way before coding the creation routine. Almost anything can be imported, though you do have to decipher the import help files. Just don't try to get any info back out through the export function. QB is loath to give out information except through dumping reports to Excel.

There is an SDK that is at version 4, I believe, that is available to developers after you do a free registration as a developer. It had VFP examples at one point. I looked at it and it was promising, but QB became too small and slow for the number of transactions that our business generates. This year we left QB behind and moved to a different software.