In the database world this is called "referential integrity" and is considered good design. There is a relationship between a transaction and a bucket. The bucket becomes a integral part of the transaction record and the database says you can't delete the bucket without first removing the relationship between the bucket and the transaction. This presents issues when designing software. If you allow deleting of buckets then the transaction looses that little bit of history abut itself, it would become unassigned.
There are ways around this by providing a means to "soft" delete a record in the database which is simply a means to remove it from view from the UI but it still lives in the database to maintain relational integrity and history. I believe MoneyWell provides for this by allowing you to set a bucket to Hidden. Once hidden it is no longer visible to everyday interaction with MW but it is still there in the database for integrity and historical purposes. The other option is to allow physical deletion but MW would have to: 1) delete all transactions related to this bucket (not really an option at all) or 2) assign the transactions that use this bucket to another bucket which is pretty nasty in it's own right from a user interaction perspective or 3) set the transactions to unassigned. As for #3, if I suddenly had 100 transactions unassigned because I deleted a bucket... well that would not make me happy. -Craig On Mar 29, 1:54 pm, Lance <[email protected]> wrote: > If you try to delete a bucket that has some other references anywhere > else in the data file, MoneyWell refuses with a system error beep and > no further details. Some of the reasons MoneyWell may refuse to delete > the bucket are more subtle than others. > > It looks like this issue was mentioned in a previous > thread:http://groups.google.com/group/no-thirst-software/browse_thread/threa... > > From my experience, I've developed a mental checklist of things to > look at when you encounter this and how to resolve them: > > 1. Does the bucket have any transactions assigned to it? Solution: > select all accounts, then select bucket from list, make sure you ARE > viewing future pending transactions, then assign any transactions that > show up to a different bucket > > 2. Does the bucket have any money flows going in/out of it? Solution: > select bucket from list, then look under "Money Flows" in the right > pane and delete any flows (they will return to the originating bucket > for redistribution). > > 3. Does the bucket have any memorized transactions assigned to it? > Solution: click on the "Memorized" tab, sort by Bucket, and delete or > reassign any that are using this bucket. > > 4. Does the bucket have any scheduled transactions assigned to it? > Solution: click on the "Scheduled" tab and manually examine each one > (unfortunately there is no Bucket column in this view!) and delete or > reassign any that are using this bucket. > > Since I assume MoneyWell is already doing these same checks when I try > to delete a bucket, I would like MoneyWell to mention which particular > check failed instead of just beeping. Also, it would be great to > describe each of these cases and how to resolve them in the help file. > The error message could then refer to this section of the help file. > > -Lance --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "No Thirst Software User Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/no-thirst-software?hl=en -~----------~----~----~----~------~----~------~--~---
