*note, while there are many ways to view the tables in one of the SQL
backends, an easy one is to use the SQLite manager plugin for Firefox
with the SQLite3 backend. (it is an older type plugin, so I keep a copy
of Waterfox Classic around to use it.)
Or you could use DBeaver database tool - Win
On 2023-12-29 22:53, Stephen wrote:
…Having the GUID … could have GUIDed me perhaps. I really appreciate
y'alls help.
I saw what you did there. Bravo!
—Jim "I am not a dad but I tell dad jokes" DeLaHunt
___
gnucash-user mailing list
Thanks everyone! Just what I needed to get over the hump. As David
Cousens wrote there is usually no need to know what these codes are or
to access them. In my case I was mostly and merely curious how things
work but I did have the idea to adjust column sizes to be uniform across
all or most
Stephen,
The GUUIDs are used internally within the GnuCash code to identify an
account/register.Each GUUID is associated with a specific account name and
position in the account tree heirarchy. There is usually no need for a user to
know what they are or to access them except in advanced debugging
That's how I would do it with the XML backend too.
If you are crafty with scripts, you can likely create a table/file,
mapping the account names to GUIDs for future reference.
or,
Switch to one of the SQL backends and write a query, or just examine the
"accounts" table directly. Of course,
Stephen:
I can't answer your question fully, but I can give you some insight.
"GUID" stands for "Globally Unique Identifier". Each GUID is a large
number, which is generated in such a way that it is highly likely to be
different than any other GUID generated on any computer at any time
