Hi Mark,
> I have ~some~ knowledge.
> In SQL, these are the 'tables' used for storage;
>> sqlite> .tables
>> accounts employees orders taxtables
>> billterms entries prices transactions
>> books gnclock recurrences vendors
>> budget_amounts gnucashew_vars schedxactions versions
>> budgets invoices slots
>> commodities jobs splits
>> customers lots taxtable_entries
> The .schema on the tables is pretty clear. The 'split's are stored in
> splits and transaction stored in transactions and so forth...
> What would you like to know?
I'm just stumbling around in the dark, picking up whatever bits of wisdom I can
find.
This was quite helpful, and I would have done it myself, had I a running
example. I am a QuickBooks refugee and after reviewing dozens of offerings, I
am beginning to conclude that GnuCash is probably the best alternative, the
whole back-end issue not withstanding. I am not "running" because migration is
a non-trivial process.
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?
_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
