Re: [GNC] Bad date not caught

2023-10-12 Thread john
There are two problems with that: Not everyone uses their locale date format. For example the US locale format is MDY but there are plenty of us former military types who do DMY because that's how the military does it. The other thing is that brain-farts happen. I enter DMY 99 44/100% of the

Re: [GNC] Bad date not caught

2023-10-12 Thread john
That would be because the FAA has been trying and failing to upgrade their IT for darn near 50 years. MMDDYY was the standard way to code dates in the 1960s. Getting that fixed was what the Y2K apocalypse was about. But while it's a nice standard that works a tread for the backends it's not

Re: [GNC] F::Q XAU & XAG quotes not retrieving for 2 years

2023-10-12 Thread Adrien Monteleone
Thanks. I'm not sure I want to get that deep into it. Yes, they were created as 'currencies' and can't be changed. I'll just manually enter prices periodically. It is only two of them. Regards, Adrien On 10/12/23 8:55 PM, Ken Farley wrote: My guess would be that it's because they were created

Re: [GNC] F::Q XAU & XAG quotes not retrieving for 2 years

2023-10-12 Thread Ken Farley
My guess would be that it's because they were created as a "currency" and can't be changed? I don't use any currencies as investments, so I don't have any experience with this kind of thing. If there is a way you can specify the source of the quotes (i.e. not Alphavantage), you could take the

Re: [GNC] Bad date not caught

2023-10-12 Thread Adrien Monteleone
I shudder at the thought, but it is entirely possible they were (and still are) 'grandfathered' in! Regards, Adrien On 10/12/23 7:02 PM, Dean Gibson wrote: This includes the US FAA. which presumes MM-DD-YY. So much for standards! I guess ISO8601 is pretty new (35 years ago) for some

Re: [GNC] Bad date not caught

2023-10-12 Thread Dean Gibson
Actually,, ISO8601 describes the valid (& preferred) date representations.  Anything with dashes is presumed to be -MM-DD.  Of course, just because this is an international standard, doesn't mean that everyone (including governments) follows it.  This includes the US FAA. which presumes

Re: [GNC] Bad date not caught

2023-10-12 Thread Stephen M. Butler
The parser should know the local date format for the user.  That would resolve the M/D/Y, D/M/Y, and Y/M/D format issue. Stephen M Butler stephen.m.butle...@gmail.com kg...@arrl.net 253-350-0166 --- GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A

Re: [GNC] Bad date not caught

2023-10-12 Thread john
Rather than banging on about the validity or lack thereof of 31 December 1999, which isn't really Fred's complaint, it would be more useful to explain that the date parser fires on every keystroke when typing a date in the Date Edit text box. That makes it unhelpful to raise a dialog every time

Re: [GNC] Closest to report date bug?

2023-10-12 Thread john
See https://netlicensing.io/blog/2012/06/15/set-environment-variables-in-windows-shortcut/ for setting an environment variable, just substitute TZ=FLE Standard Time for LANG=en. There's a list of all of the Windows Timezone names at

Re: [GNC] Closest to report date bug?

2023-10-12 Thread Marta Neeziak
I'll try to figure out the TZ environment variable on my end - is there a standard path where I'd find the file to be modified? For reference, I'm on Windows 10. And yes, Last Before doesn't seem to increment by date and just uses the last security price found in the Price DB. Thanks for the

Re: [GNC] Closest to report date bug?

2023-10-12 Thread john
You can use the TZ environment variable to run GnuCash in a different timezone from the system. Last Before should operate on the increment date for time series just like Closest to. Chris Lam, can you take a look at that? Regards, John Ralls > On Oct 11, 2023, at 18:47, Marta Neeziak wrote:

Re: [GNC] Bad date not caught

2023-10-12 Thread Michael or Penny Novack
On 10/12/2023 10:40 AM, Fred Tydeman wrote: In an account, I clicked on Duplicate of a transaction. I got a small popup with the date field highlighted. I typed in 5.19.21 (instead of the correct 5/19/21) and pressed enter. That got me the transaction duplicated, but with the date of

Re: [GNC] Bad date not caught

2023-10-12 Thread Derek Atkins
Hi, On Thu, October 12, 2023 10:40 am, Fred Tydeman wrote: > In an account, I clicked on Duplicate of a transaction. > I got a small popup with the date field highlighted. > I typed in 5.19.21 (instead of the correct 5/19/21) and pressed enter. > That got me the transaction duplicated, but with

[GNC] Bad date not caught

2023-10-12 Thread Fred Tydeman
In an account, I clicked on Duplicate of a transaction. I got a small popup with the date field highlighted. I typed in 5.19.21 (instead of the correct 5/19/21) and pressed enter. That got me the transaction duplicated, but with the date of 12/31/1969. Seems like the code should warn me about bad

[GNC] tax report for india

2023-10-12 Thread Paras Desai
Hello Adrien, Thanks for your reply. Much appreciate. I was running the transaction report, without selecting child account (I assumed that by selecting “Income” account all children accounts would be selected automatically, but that was not the case). I selected all the children accounts

Re: [GNC] macOS Sonoma "Gnucash is damaged and can’t be opened" error

2023-10-12 Thread Adrien Monteleone
I'm suspicious of a missing step. Did you *install* Gnucash, or just download the .dmg file and open it, then click Gnucash.app? The .dmg file, when opened should have a shortcut to /Applications to make it handy to drag the Gnucash.app file over it for installation, and even has an arrow