Predicting Future Minimum Balance

Brian Dolbec brian_dolbec at telus.net
Thu Sep 14 19:57:19 EDT 2006


On Thu, 2006-14-09 at 13:20 -0500, Dale Alspach wrote:
> A crude approach would be to just clone the gnucash data file (and
> ancillaries) under a new name, run the SX or other "what if" transactions on
> the clone, do reports on the clone, save the report output if desired, and
> then blow all of the cloned stuff away until the next "what if" session.
> 
> There could just be a "what if" menu choice which does all the cloning.
> Maybe there could be a color change (border, backgrounds?) to visually show that the user is no
> longer working  on the real file. When the user wants to end the "what if", 
> he is asked what to save and then gnucash destroys the files from the 
> clone or renames as directed by the user.
> 
> 
> Dale Alspach
> 

What about a graph with time for the x axis and value the y.  Of course
that would go along with the budget data so that anything future dated
would use the budget data along with non-dupe sx's.

-- 
Brian Dolbec <brian_dolbec at telus.net>



More information about the gnucash-user mailing list