On 13 June 2020 at 16:02, Stan Brown said:
>
> On 2020-06-13 15:17, Robert Smits wrote:
> > On October 16, 2017 08:18:49 am baneeishaque wrote:
> >> Solved the problem in aneasier way...
>
> Well, don't leave us in suspense! What was your solution?
Maf.King asked, back when the message was
On 2020-06-13 15:17, Robert Smits wrote:
> On October 16, 2017 08:18:49 am baneeishaque wrote:
>> Solved the problem in aneasier way...
Well, don't leave us in suspense! What was your solution?
--
Regards,
Stan Brown
Tehachapi, CA, USA
https://BrownMath.com
https://OakRoadSystems.com
On October 16, 2017 08:18:49 am baneeishaque wrote:
> Solved the problem in aneasier way...
>
>
>
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
>
I too would be interested in the mystery solution.
Personally I use the 24hour time without a separator—e.g. 5:32pm becomes 1732.
To distinguish times from other numbers I use “T” at the end, thus: 1732T
However, this breaks if there are actual numbers to enter like from a check. I
have so few
On Monday, 16 October 2017 16:18:49 BST baneeishaque wrote:
> Solved the problem in aneasier way...
>
OK. I'll bite.
What is the easier way?Others in the future might benefit from your method?
BTW, happy to hear that you found a solution.
Cheers,
Maf.
Solved the problem in aneasier way...
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to
