No-one?
Oh dear.
I'm lost in a maze of different file imports, all alike....

Hi Iain

I'm "west of the house" dying to reach the kitchen.

Sorry, but what is "quickbook" (haven't heard of so far)?

SUccess, Uli

Quickbooks is (apparently) the de-facto small business accountancy package in the U.S.
It appears to be able to interface in CSV, XLS, IIF (Propriatory tab separated format) and COM.

Uniface is, of course, only of use in the COM implementation until it reaches a 'branched' method (returning different types of results), where the imported signature breaks down and it becomes overly onerous adding each operation separately. Unless someone knows whether you can somehow kick the import off again from a new point....

I am currently beating my way through writing a c# wrapper dll. I think it will work, but I can't get an importable signature.

I'd obviously like the COM interface, as it would provide 'seamless' integration between my Application and the ledgers.

Hi Iain,

I would shoot for some kind of parser where I can transfer the complete file to an XML, a uniface list or so.

and for another to transfer this list/XML etc. to the interchange format.

I have done this for a couple of interchange formats and given a global routine, it is pretty flexible.

Perhaps you can give me some interface descriptions mailto:ulrichmerkel@web.de

SUccess, Uli

Hmm, it won't let me reply to Uli for some reason. Just thrown three answers away. So....

Uli, I have no problem writing the text file outputs if I need to. I simply don't know what the 'correct' interface format is. The QB interface format is sufficiently flexible as to require a working knowledge of both QB and U.S. Accountancy practices in order to decide what data needs to be transferred. (You can specify all the columns you want to transfer over, with no clues in the documentation which ones are mandatory and which ones are advisable...)

As it happens, I would prefer to use the COM interface, as this will allow for inline checking and data validation, and prevent the usual errors of file locations and obsolete copies due to manual error in the transfer process.

However, I am stymied, (as usual) by there being no practical documentation on how to produce a Uniface compatible dll. See attached thread (assuming I manage to attach it) for details.

Hi Iain,

think you are looking in the wrong area:

As soon as you have an OCX/COM widget,

you can bind it to an OCX container and communicate with the QB.

The documentation I found so far is about a flexible way of transfering any kind of data,

but as you stated, nothing is said which data are mandatory etc.

The only one: it has to be accepted by the QB Server.

SO what is necessary in the dialog window,

is necessary in the file/communication.

Have a good QB manual or give it a try.

Success, Uli