Custom Field (Decimal)

Mac OS X 10.9 or higher.

Moderator: Renato

Post Reply
Wirmike
Super MMEX User
Posts: 59
Joined: Sat Oct 02, 2010 6:04 pm
Are you a spam bot?: No

Custom Field (Decimal)

Post by Wirmike »

I have started to put into place a marvellous new use to put Custom Fields to.

However, a major issue has arisen.

I am using fields set to Decimal w/- the ‘scale’ set to 2 Decimal Places.
Values in this field type may well frequently exceed 1,000.00.
Any value in the interval [0.00,999,99] will be successfully stored and displayed as such when the transaction is opened after Okay-ing

As the function of this field is to record a monetary value, then I would think that it should have the capability of recording the same range of values as in the other money fields in the transaction.

The Issue:
—————-
However, when attempting to input a value >999.99 fails and returns a field vale of 0.00 when viewing the transaction after Okay-ing.
Can you advise?

Question:
—————
Are Custom Fields protected against accidental deletion if there are data in those fields in other transactions - in a similar way to that offered to Categories in the transaction ‘proper’?
If not, can it be provided?

I am using the latest stable release 1.5.18.

Regards
MartinArmstrong
Super MMEX User
Posts: 135
Joined: Tue Mar 02, 2021 10:24 am
Are you a spam bot?: No

Re: Custom Field (Decimal)

Post by MartinArmstrong »

Bug confirmed.

I've raised an issue: https://github.com/moneymanagerex/money ... ssues/4921

Are Custom Fields protected against accidental deletion if there are data in those fields in other transactions - in a similar way to that offered to Categories in the transaction ‘proper’?
If not, can it be provided?
No, they are not protected in the manner you describe. You always get a deletion confirmation message, with a default action of No, regardless of whether the field is in use by transactions or not.
CF_deletion.png
CF_deletion.png (13.96 KiB) Viewed 254 times

For the moment you need to be careful when you delete custom fields.

But a question for you: Why would you need to delete a custom field anyway? If you have created it to use in transactions, then presumably it has meaning for those transactions, so why would you ever want to delete it? There's no problem with 'storage space' in the database.
Wirmike
Super MMEX User
Posts: 59
Joined: Sat Oct 02, 2010 6:04 pm
Are you a spam bot?: No

Re: Custom Field (Decimal)

Post by Wirmike »

Thank you for confirming and referring the Bug.

Re Custom Fields deleting.

To answer your question…
.. quite simply to guard against accidents - those times when one wishes that a little cleverness in coding may have guarded against one’s mental clumsiness. That is surely one advantage that computerisation makes possible.
An early introduction to me in coding Safeguarding data was in the CP/M days when ERA *.* was met w/- the cautionary question, “ALL FILES Y/N?” There has always been a need to minimise, neh, prevent a digital disaster - IRMC.

Regards.
whall3y
MMEX Developer
Posts: 297
Joined: Fri Aug 21, 2020 5:44 pm
Are you a spam bot?: No

Re: Custom Field (Decimal)

Post by whall3y »

Wirmike wrote: Mon Aug 08, 2022 9:13 pm Thank you for confirming and referring the Bug.

Re Custom Fields deleting.

To answer your question…
.. quite simply to guard against accidents - those times when one wishes that a little cleverness in coding may have guarded against one’s mental clumsiness. That is surely one advantage that computerisation makes possible.
An early introduction to me in coding Safeguarding data was in the CP/M days when ERA *.* was met w/- the cautionary question, “ALL FILES Y/N?” There has always been a need to minimise, neh, prevent a digital disaster - IRMC.

Regards.
But you do get that equivalent message.....
MartinArmstrong
Super MMEX User
Posts: 135
Joined: Tue Mar 02, 2021 10:24 am
Are you a spam bot?: No

Re: Custom Field (Decimal)

Post by MartinArmstrong »

Wirmike wrote: Mon Aug 08, 2022 9:13 pm To answer your question…
.. quite simply to guard against accidents - those times when one wishes that a little cleverness in coding may have guarded against one’s mental clumsiness.
As @whall3y (and I) have said, you do get a very clear "do you really want to delete?" message (with a default response of 'No') and you have the safety net of automatic database backups.

If you haven't enabled these in Options, you should do so.

mmex backup.png
mmex backup.png (15.4 KiB) Viewed 203 times
By renaming a .bak backup to be your current .mmb and opening that database, it is trivial to recover from accidents.

If you haven't tried this already, then I'd advise that you create a new test.mmb database (or copy & rename your main database if you wish) and then experiment with 'making a mistake' and recovering the previous version of your database.
Post Reply