|
#10
| |||
| |||
| Not likely. But I could be wrong. "pfanelli" <pfanelli[at]discussions.microsoft.com> wrote in message news:4CB73CF4-3CF7-4CBC-92CA-E14839597D17[at]microsoft.com... - quote - > This is one of the most helpful post strings - thanks for the information. > Do you suppose the 'nuke' will solve this? > I have several loan accounts with the payment set up in the bill section. > Sometimes - but not all the time - the program will get confused when I > execute the payment and will forget how to calculate interest and > principle. > Instead, it will post the entire amount in the principle category. |
|
#9
| |||
| |||
| This is one of the most helpful post strings - thanks for the information. Do you suppose the 'nuke' will solve this? I have several loan accounts with the payment set up in the bill section. Sometimes - but not all the time - the program will get confused when I execute the payment and will forget how to calculate interest and principle. Instead, it will post the entire amount in the principle category. "Dick Watson" wrote: - quote - > Once all of the series exceptions are entered in register or deleted, what's > to keep track of? Instead of yet another utility, why can't they just make > it cleanup after itself on the fly? The number of exceptions should NEVER > exceed 12x the number of bills since each bill can only have the next twelve > series members edited to be exceptions. > As usual, I probably don't understand how they've really designed the > innards, but it just doesn't seem like that hard of a problem... > "Bob Peel, MVP" <bob_peel[at]kiandra.freeserve.co.uk.INVALID> wrote in message > news:O3Dk3foCIHA.4360[at]TK2MSFTNGP06.phx.gbl... > > Logically however there is going to be a time when the number of schemas > > builds up and another Nuking session is needed. > > > Hopefully MS will produce an utility to achieve this. I have no insights > > as to whether this is planned or is indeed feasible. |
|
#8
| |||
| |||
| Once all of the series exceptions are entered in register or deleted, what's to keep track of? Instead of yet another utility, why can't they just make it cleanup after itself on the fly? The number of exceptions should NEVER exceed 12x the number of bills since each bill can only have the next twelve series members edited to be exceptions. As usual, I probably don't understand how they've really designed the innards, but it just doesn't seem like that hard of a problem... "Bob Peel, MVP" <bob_peel[at]kiandra.freeserve.co.uk.INVALID> wrote in message news:O3Dk3foCIHA.4360[at]TK2MSFTNGP06.phx.gbl... - quote - > Logically however there is going to be a time when the number of schemas > builds up and another Nuking session is needed. > Hopefully MS will produce an utility to achieve this. I have no insights > as to whether this is planned or is indeed feasible. |
|
#7
| |||
| |||
| The performance problems that Nuke The Bills solves are much more pervasive that the problems that Spending Tracker is causing on some people's home pages. "Fran Menzel" <FranMenzel[at]discussions.microsoft.com> wrote in message news:57900D62-EA8F-44D7-8BA6-805CF883E2C2[at]microsoft.com... - quote - > There are a couple of threads relating to Money Plus complaining about > poor > performance. Folks have found that spending tracker is a major culprit. > I > recemtly did the same upgrade as you, and although my system is clearly > speedier, Plus takes 10 vs 1 minute to fill in the home page. Please join > me > in insisting that Microsoft fix the problem. I have no intention of > streamlining my file to fix their performance issue. |
|
#6
| |||
| |||
| There is no good way that gets all of the information. This is another area where Money borders on a Write Only Memory. Barring availability of two machines running Money that can Remote Desktop (so you can copy from one Money session with the old bills stuff to the other Money session where you are re-entering the bills stuff) I would print and/or Export to Excel a report the Scheduled Bills report (can't remember it's exact name). To this I would mark up or note in the resultant Excel file all of the stuff that doesn't report. (Any exceptions in the series, the flag for "amount varies" and any series "ends after" information all come to mind as things that don't report.) "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message news:53B4F20D-D893-4452-AF83-55831C3D3520[at]microsoft.com... - quote - > What is the best way to export the Bills information? |
|
#5
| |||
| |||
| Jeff <Jeff[at]discussions.microsoft.com> wrote: - quote - > What is the best way to export the Bills information?
Did this a couple of months back, and it made a huge difference. Money isactually usable again. I believe there's a report in the Bills section - you can just use File|Print to get most of the useful information you'll need to recreate them. I don't think there's a way to export / nuke / import - you'll have to rebuild. It does speed up the rebuild process though if you can go through your check register and use 'make recurring' on things like utility bills, etc. You can at least leverage your history. -Brent |
|
#4
| |||
| |||
| As I understand it every time you amend a bill (frequency or amount) a new bill schema is created. When examining bills Money has to wander through all schemas tracking current bills. Thus if your bills are regular/static then the Nuking effect will last. Logically however there is going to be a time when the number of schemas builds up and another Nuking session is needed. Hopefully MS will produce an utility to achieve this. I have no insights as to whether this is planned or is indeed feasible. -- Regards Bob Peel, Microsoft MVP - Money For UK tips & fixes see http://support.microsoft.com/default...d=fh;EN-GB;mny. I do not respond to any emails that I have not specifically asked for. "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message news:8F2D0CEA-D7FF-414C-84DD-F44BB67586A3[at]microsoft.com... - quote - > Dick > thanks! > Niking the bills appears to have resolved the issues > However will adding thme back in bring the problems back? > Jeff > "Dick Watson" wrote: > > Consider Nuke The Bills. See http://umpmfaq.info/faqdb.php?q=187. It has > > worked for a lot of people. You might want to try it first on a COPY of > > your > > data file to see if it solves anything before committing to all of the > > effort it takes to really do it on your production file. Dumping to QIF > > does > > not make sense as way too many things do not go through that filter. > > (Bills, > > Loan Accounts, and details for Accounts, Payees, Categories, and > > classifications to name just a few.) > > > "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message > > news:597B8353-2C90-49F8-9F83-23C58426F70B[at]microsoft.com... > > > I recently upgrade from Money 2005 to 2008 > > > My Money DB has been around since ~2001 and is over 25 MB > > > When I was running 2005 there were many times when Money would just peg > > > the > > > CPU and churn away. > > > This seems to be MUCH worse with 2008; when I startup it just churns > > > for > > > 10 > > > minutes > > > > > I was thinking of starting my DB over. > > > I thought I would export the data from my current file as .qif > > > Edit the quif to remove anyhting prior to 2006 > > > Then reimport into 2008 > > > > > Does this make sense? > > > Any other suggestions are welcome > > > |
|
#3
| |||
| |||
| Dick What is the best way to export the Bills information? Jeff "Dick Watson" wrote: - quote - > Consider Nuke The Bills. See http://umpmfaq.info/faqdb.php?q=187. It has > worked for a lot of people. You might want to try it first on a COPY of your > data file to see if it solves anything before committing to all of the > effort it takes to really do it on your production file. Dumping to QIF does > not make sense as way too many things do not go through that filter. (Bills, > Loan Accounts, and details for Accounts, Payees, Categories, and > classifications to name just a few.) > "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message > news:597B8353-2C90-49F8-9F83-23C58426F70B[at]microsoft.com... > > I recently upgrade from Money 2005 to 2008 > > My Money DB has been around since ~2001 and is over 25 MB > > When I was running 2005 there were many times when Money would just peg > > the > > CPU and churn away. > > This seems to be MUCH worse with 2008; when I startup it just churns for > > 10 > > minutes > > > I was thinking of starting my DB over. > > I thought I would export the data from my current file as .qif > > Edit the quif to remove anyhting prior to 2006 > > Then reimport into 2008 > > > Does this make sense? > > Any other suggestions are welcome |
|
#2
| |||
| |||
| Dick thanks! Niking the bills appears to have resolved the issues However will adding thme back in bring the problems back? Jeff "Dick Watson" wrote: - quote - > Consider Nuke The Bills. See http://umpmfaq.info/faqdb.php?q=187. It has > worked for a lot of people. You might want to try it first on a COPY of your > data file to see if it solves anything before committing to all of the > effort it takes to really do it on your production file. Dumping to QIF does > not make sense as way too many things do not go through that filter. (Bills, > Loan Accounts, and details for Accounts, Payees, Categories, and > classifications to name just a few.) > "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message > news:597B8353-2C90-49F8-9F83-23C58426F70B[at]microsoft.com... > > I recently upgrade from Money 2005 to 2008 > > My Money DB has been around since ~2001 and is over 25 MB > > When I was running 2005 there were many times when Money would just peg > > the > > CPU and churn away. > > This seems to be MUCH worse with 2008; when I startup it just churns for > > 10 > > minutes > > > I was thinking of starting my DB over. > > I thought I would export the data from my current file as .qif > > Edit the quif to remove anyhting prior to 2006 > > Then reimport into 2008 > > > Does this make sense? > > Any other suggestions are welcome |
|
#1
| |||
| |||
| There are a couple of threads relating to Money Plus complaining about poor performance. Folks have found that spending tracker is a major culprit. I recemtly did the same upgrade as you, and although my system is clearly speedier, Plus takes 10 vs 1 minute to fill in the home page. Please join me in insisting that Microsoft fix the problem. I have no intention of streamlining my file to fix their performance issue. "Jeff" wrote: - quote - > I recently upgrade from Money 2005 to 2008 > My Money DB has been around since ~2001 and is over 25 MB > When I was running 2005 there were many times when Money would just peg the > CPU and churn away. > This seems to be MUCH worse with 2008; when I startup it just churns for 10 > minutes > I was thinking of starting my DB over. > I thought I would export the data from my current file as .qif > Edit the quif to remove anyhting prior to 2006 > Then reimport into 2008 > Does this make sense? > Any other suggestions are welcome > Jeff |
| | |||
| |||
| Consider Nuke The Bills. See http://umpmfaq.info/faqdb.php?q=187. It has worked for a lot of people. You might want to try it first on a COPY of your data file to see if it solves anything before committing to all of the effort it takes to really do it on your production file. Dumping to QIF does not make sense as way too many things do not go through that filter. (Bills, Loan Accounts, and details for Accounts, Payees, Categories, and classifications to name just a few.) "Jeff" <Jeff[at]discussions.microsoft.com> wrote in message news:597B8353-2C90-49F8-9F83-23C58426F70B[at]microsoft.com... - quote - > I recently upgrade from Money 2005 to 2008 > My Money DB has been around since ~2001 and is over 25 MB > When I was running 2005 there were many times when Money would just peg > the > CPU and churn away. > This seems to be MUCH worse with 2008; when I startup it just churns for > 10 > minutes > I was thinking of starting my DB over. > I thought I would export the data from my current file as .qif > Edit the quif to remove anyhting prior to 2006 > Then reimport into 2008 > Does this make sense? > Any other suggestions are welcome |
|
#-1
| |||
| |||
| I recently upgrade from Money 2005 to 2008 My Money DB has been around since ~2001 and is over 25 MB When I was running 2005 there were many times when Money would just peg the CPU and churn away. This seems to be MUCH worse with 2008; when I startup it just churns for 10 minutes I was thinking of starting my DB over. I thought I would export the data from my current file as .qif Edit the quif to remove anyhting prior to 2006 Then reimport into 2008 Does this make sense? Any other suggestions are welcome Jeff |