Ha - that's this very thread!
Sorry for the noise.
Regards,
Adrien
On 5/2/23 7:45 AM, Adrien Monteleone wrote:
Someone reported that the CSV importer was adding to placeholders as well.
Perhaps these issues are related to the same code block.
Regards,
Adrien
On 5/1/23 2:06 PM, David T. via
Someone reported that the CSV importer was adding to placeholders as well.
Perhaps these issues are related to the same code block.
Regards,
Adrien
On 5/1/23 2:06 PM, David T. via gnucash-user wrote:
I'm going to follow up my own message to note that I have now found that
GnuCash 4.13 under
I'm going to follow up my own message to note that I have now found that
GnuCash 4.13 under Windows 10 will add transactions to a placeholder account
even while displaying a message stating that it cannot write transactions to
placeholder accounts!
I've just had GnuCash do this twice, when it
Michael,
The OP problem had to do with the importer adding transactions to a placeholder
account. So that's why I am discussing that, rather than bringing up the
creation of new accounts in the process. I'm not even sure how that applies
here; a newly-created account during the import process
On 2023-04-29 08:17, Michael or Penny Novack wrote:
> And an operating system SHOULD allow writing into a write protected
> folder whenever the person (or program) doing so has sufficient "rights"
Oh dear no. It should let someone with privilege write into the folder
_after requiring the user to
On 4/29/2023 10:08 AM, David T. wrote:
Michael,
I disagree. The importer shouldn't put transacting into an account
that is--by definition-- write protected.
My counter example would be a write-protected file folder. An
operating system that allowed a user to put data into a
write-protected
Michael,
I disagree. The importer shouldn't put transacting into an account that is--by
definition-- write protected.
My counter example would be a write-protected file folder. An operating system
that allowed a user to put data into a write-protected folder would come in for
serious
On 4/29/2023 2:39 AM, David T. via gnucash-user wrote:
There's no hard rule either way. Some users feel strongly about not having any
transactions in placeholder accounts, though, and advocate loudly on the list
in support of it. But there's nothing in the software preventing a placeholder
There's no hard rule either way. Some users feel strongly about not having any
transactions in placeholder accounts, though, and advocate loudly on the list
in support of it. But there's nothing in the software preventing a placeholder
account having transactions in it.
That said, the
My understanding is Placeholder accounts should have zero transactions in
them.
However, when I Import a QIF file, sometimes I end up with transactions in
a Placeholder account.
It would be nice if the importer would give a warning about putting
transactions into a Placeholder account. That
10 matches
Mail list logo
