Sound advice. Doing QIF sounds a bit easier than linking the libraries (and maintaining it) and may suffice for my particular needs. The problem I contemplate will be not in the individual line-item GL transactions, but in creating a QIF invoice that could be edited and/or printed.
Does Gnucash import invoices? ----- Original Message ----- That's separate from our telling people who want to extend Gnucash that they mustn't write directly to storage without using the API. We know that if they write directly to storage they'll write unbalanced transactions, or miss some critical bit of metadata, or simply write a record that's different from the way Gnucash does, and then we'll have users complaining that Gnucash can't read its data. In the past, people who've wanted to write data have had in mind small extensions to Gnucash, generally for personal use. You implied a rather more ambitious project. As for your POS import, the safest way to implement that would be either: * have the POS system export a format that Gnucash can import -- Derek always recommends QIF * if you want to get really fancy, give it an OFXdirect or HCBI interface and use Gnucash's online banking features (implemented through AQBanking -- Martin Preuß might be able to help you with the POS's server side as well). Aside from not driving yourself insane trying to track our API, either of those would afford the advantage of working with other accounting programs. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
