|
#10
| |||
| |||
| Chris, please take no offense. I am being angry at Money - not at you. -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services "Chris Cowles" <spam_magnet[at]remove-me-bellsouth.net> wrote in message news:OMDcwDRJGHA.2668[at]tk2msftngp13.phx.gbl... - quote - > "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message > news:Oiovg5QJGHA.1288[at]TK2MSFTNGP09.phx.gbl... > > > I hope you won't call this also a "feature" of money and not a bug? > I'm not an apologist. I've simply described the way it works. If you don't > like my suggestions and descriptions, tell me, and I will cease to provide > them. > -- > Chris Cowles > Gainesville, FL |
|
#9
| |||
| |||
| "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:Oiovg5QJGHA.1288[at]TK2MSFTNGP09.phx.gbl... - quote - > I hope you won't call this also a "feature" of money and not a bug?
I'm not an apologist. I've simply described the way it works. If you don'tlike my suggestions and descriptions, tell me, and I will cease to provide them. -- Chris Cowles Gainesville, FL |
|
#8
| |||
| |||
| They're having enough trouble making a business case for the product as it is. "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:Oiovg5QJGHA.1288[at]TK2MSFTNGP09.phx.gbl... - quote - > This product is just not ready for the market. It should not be sold; > instead, its alpha-testers should be paid for using it. |
|
#7
| |||
| |||
| Neither way. The problem finally solved by first deleting deposit series at all. That caused "haunted" budget entry, described in another post. I hope you won't call this also a "feature" of money and not a bug? The only way to finally get out of it was to delete and never use the income category this darn deposit was assigned to, and create another scheduled depo using different category. This product is just not ready for the market. It should not be sold; instead, its alpha-testers should be paid for using it. -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services "Chris Cowles" <spam_magnet[at]remove-me-bellsouth.net> wrote in message news:OcWiW0PJGHA.596[at]TK2MSFTNGP10.phx.gbl... - quote - > "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message > news:Om6IW8LJGHA.1028[at]TK2MSFTNGP11.phx.gbl... > > > It was money's ASSUMPTION to enter this deposit to the budget based on > > the schedule I've created. > That is correct. From Money's perspective, you told it to do that, because > that's what it always does with scheduled bills. Some like it, some hate > it. Everybody lives with it. > > > After Jan's occurence has already been entered in late Dec, I EXPECT > > money to be smart and RECONSIDER it's assumptions on the upcoming > > deposits. > Don't. > > In other words, since the Jan's occurense has already happened earlier, > > and money already knows of that, it should have REMOVED its corresponding > > assumption from the Jan's budget. > It won't. > > So what work-around do you offer? Edit the single occurence of the > > scheduled deposit so money could adequately calculate budget? > Yes. Before recording the deposit. But beware that, once you do that, > every future event is now considered a separate event. It's a conundrum. > > Shouldn't money just DO IT BY ITSELF when I enter this occurence to the > > register? > Not necessarily. Budgets, in the minds of some, are static projections as > to what's expected to happen. Your deposit deviated from the budget. You > don't necessarily adjust the budget to reflect actuals. If you did, how > would you ever know you were deviating from the budget, because it would > always reflect actual, not the plan. > > Isn't it what computer programs are for - to save us time by automating > > routing actions? > Yes, but Money's treatment of the budget would be considered appropriate > by some and is neither right nor wrong. It's how it works. > -- > Chris Cowles > Gainesville, FL |
|
#6
| |||
| |||
| "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:Om6IW8LJGHA.1028[at]TK2MSFTNGP11.phx.gbl... - quote - > It was money's ASSUMPTION to enter this deposit to the budget based on the
That is correct. From Money's perspective, you told it to do that, because> schedule I've created. that's what it always does with scheduled bills. Some like it, some hate it. Everybody lives with it. - quote - > After Jan's occurence has already been entered in late Dec, I EXPECT money
Don't.> to be smart and RECONSIDER it's assumptions on the upcoming deposits. - quote - > In other words, since the Jan's occurense has already happened earlier,
It won't.> and money already knows of that, it should have REMOVED its corresponding > assumption from the Jan's budget. - quote - > So what work-around do you offer? Edit the single occurence of the
Yes. Before recording the deposit. But beware that, once you do that, every> scheduled deposit so money could adequately calculate budget? future event is now considered a separate event. It's a conundrum. - quote - > Shouldn't money just DO IT BY ITSELF when I enter this occurence to the
Not necessarily. Budgets, in the minds of some, are static projections as to> register? what's expected to happen. Your deposit deviated from the budget. You don't necessarily adjust the budget to reflect actuals. If you did, how would you ever know you were deviating from the budget, because it would always reflect actual, not the plan. - quote - > Isn't it what computer programs are for - to save us time by automating
Yes, but Money's treatment of the budget would be considered appropriate by> routing actions? some and is neither right nor wrong. It's how it works. -- Chris Cowles Gainesville, FL |
|
#5
| |||
| |||
| Chris - I did not TELL money to expect deposit in January and enter it into the budget. It was money's ASSUMPTION to enter this deposit to the budget based on the schedule I've created. After Jan's occurence has already been entered in late Dec, I EXPECT money to be smart and RECONSIDER it's assumptions on the upcoming deposits. In other words, since the Jan's occurense has already happened earlier, and money already knows of that, it should have REMOVED its corresponding assumption from the Jan's budget. It's just silly, money automatically adds to the budget transation that money KNOWS are going to happen, so why it doesn't remove from the budget transaction that money ALSO KNOWS aren't going to happen anymore? OK, let's stop discussing Money's bug here. We both know money is a very buggy program. There are many things which don't exist or don't work. For example, it's just silly that I cannot schedule a deposit in a currency different from the currency of the account this deposit goes to. Same silly as the budget case we've been discussing. So what work-around do you offer? Edit the single occurence of the scheduled deposit so money could adequately calculate budget? Shouldn't money just DO IT BY ITSELF when I enter this occurence to the register? Isn't it what computer programs are for - to save us time by automating routing actions? -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services "Chris Cowles" <spam_magnet[at]remove-me-bellsouth.net> wrote in message news:ul38OMDJGHA.2320[at]TK2MSFTNGP11.phx.gbl... - quote - > "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message > news:eXx$Yv$IGHA.2928[at]TK2MSFTNGP10.phx.gbl... > > I did not edit deposit schedule, nor dit I adjust any budgets. Also, I > > didn't enter any deposits to the budget - they get entered there > > automatically. > > > What I cant understand is that even thou Money can track deposit > > transactions normally sometimes - I've entered Jan's transaction earlier, > > and money doesn't expect it occur on Jan anymore - it can't do it all the > > way. > > > Money IS NOT expecting this deposit in january. It was correctly entered > > into the register in late december; next occurence of this deposit is > > shown at Feb. It is correct. Everything but the budget. Jan's budget > > still thinks there should be a deposit transaction in Jan, even thou > > Money KNOWS this transaction has already occured in late Dec. > The budget, i.e., what you told Money to expect, and the register, what > actually happened, are two different things. You told Money to expect a > deposit in January. You didn't change its expectation when you recorded > the deposit. You merely changed the date of the actual deposit. > Had you revised the scheduled deposit IN ADVANCE, then saved it, the > budget would then expect the deposit on the date you told it. Then, when > you actually received and recorded the deposit, it would have been > associated correctly. Once recorded, the scheduled budget dates are not > accessible for revision. > Instead, what apparently happened is you scheduled a monthly deposit. > Let's assume there are 3 events for the deposit and call them deposit > numbers 1, 2, and 3. Money automatically adopted them in the budget for > January, February, and March. The fact you received and recorded January's > deposit with a December date does not revise the expected date recorded in > the budget. > You CAN revise individual scheduled events of a series. That could have > resulted in your January deposit being expected in December, and the > remaining February and March deposits remaining in the budget months > originally scheduled. There are reasons to do so, and there are reasons > not to do so, i.e., potential problems. Those are outside the scope of > this specific topic. > -- > Chris Cowles > Gainesville, FL |
|
#4
| |||
| |||
| "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:eXx$Yv$IGHA.2928[at]TK2MSFTNGP10.phx.gbl... - quote - > I did not edit deposit schedule, nor dit I adjust any budgets. Also, I
The budget, i.e., what you told Money to expect, and the register, what> didn't enter any deposits to the budget - they get entered there > automatically. > What I cant understand is that even thou Money can track deposit > transactions normally sometimes - I've entered Jan's transaction earlier, > and money doesn't expect it occur on Jan anymore - it can't do it all the > way. > Money IS NOT expecting this deposit in january. It was correctly entered > into the register in late december; next occurence of this deposit is > shown at Feb. It is correct. Everything but the budget. Jan's budget still > thinks there should be a deposit transaction in Jan, even thou Money KNOWS > this transaction has already occured in late Dec. actually happened, are two different things. You told Money to expect a deposit in January. You didn't change its expectation when you recorded the deposit. You merely changed the date of the actual deposit. Had you revised the scheduled deposit IN ADVANCE, then saved it, the budget would then expect the deposit on the date you told it. Then, when you actually received and recorded the deposit, it would have been associated correctly. Once recorded, the scheduled budget dates are not accessible for revision. Instead, what apparently happened is you scheduled a monthly deposit. Let's assume there are 3 events for the deposit and call them deposit numbers 1, 2, and 3. Money automatically adopted them in the budget for January, February, and March. The fact you received and recorded January's deposit with a December date does not revise the expected date recorded in the budget. You CAN revise individual scheduled events of a series. That could have resulted in your January deposit being expected in December, and the remaining February and March deposits remaining in the budget months originally scheduled. There are reasons to do so, and there are reasons not to do so, i.e., potential problems. Those are outside the scope of this specific topic. -- Chris Cowles Gainesville, FL |
|
#3
| |||
| |||
| I did not edit deposit schedule, nor dit I adjust any budgets. Also, I didn't enter any deposits to the budget - they get entered there automatically. What I cant understand is that even thou Money can track deposit transactions normally sometimes - I've entered Jan's transaction earlier, and money doesn't expect it occur on Jan anymore - it can't do it all the way. Money IS NOT expecting this deposit in january. It was correctly entered into the register in late december; next occurence of this deposit is shown at Feb. It is correct. Everything but the budget. Jan's budget still thinks there should be a deposit transaction in Jan, even thou Money KNOWS this transaction has already occured in late Dec. -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services "Chris Cowles" <spam_magnet[at]remove-me-bellsouth.net> wrote in message news:%23pTwT22GGHA.1100[at]TK2MSFTNGP10.phx.gbl... - quote - > "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message > news:eUQk61zGGHA.312[at]TK2MSFTNGP09.phx.gbl... > > Nope, I've entered the deposit from the scheduled bills/deposits page - > > the scheduled trans is not on the list. It was correctly entered into the > > register. > When you entered the deposit, did you do it through the scheduled bill? > I think what's happening is that you told the budget there would be a > deposit in January. Then you recorded a deposit in December. Unless you > adjusted your budget beforehand by, say, editing the single deposit > schedule and saving the schedule before recording it, Money's still > expecting a deposit in January. > -- > Chris Cowles > Gainesville, FL |
|
#2
| |||
| |||
| "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:eUQk61zGGHA.312[at]TK2MSFTNGP09.phx.gbl... - quote - > Nope, I've entered the deposit from the scheduled bills/deposits page -
When you entered the deposit, did you do it through the scheduled bill?> the scheduled trans is not on the list. It was correctly entered into the > register. I think what's happening is that you told the budget there would be a deposit in January. Then you recorded a deposit in December. Unless you adjusted your budget beforehand by, say, editing the single deposit schedule and saving the schedule before recording it, Money's still expecting a deposit in January. -- Chris Cowles Gainesville, FL |
|
#1
| |||
| |||
| Nope, I've entered the deposit from the scheduled bills/deposits page - the scheduled trans is not on the list. It was correctly entered into the register. -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services "Chris Cowles" <NoSpam[at]For.me> wrote in message news:%238xD91WDGHA.2072[at]TK2MSFTNGP09.phx.gbl... - quote - > "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message > news:%23GoI5tSDGHA.532[at]TK2MSFTNGP15.phx.gbl... > > I have a recurring deposit set up each month for 14th. Now that this > > deposit actually arrived at December 29th instead of next year's Jan 14th, > > I've entered the next occurence (scheduled at Jan 14) into the register, > > using Dec 29 date. > > > Everything is fine, BUT the budget for the Jan does not take this into > > account. It still thinks there is going to be deposit at Jan 14 - even > > thou it has been received earlier by Dec 29 and entered into the > > register. > > > Is it a known bug? I am usind Deluxe 2006 trial version. > Did you record the deposit in the register and not match it to the > scheduled transaction? Is the scheduled transaction still in the bills > list? |
| | |||
| |||
| "Dmitry Korolyov [MVP]" <d__k[at]removethispart.mail.ru> wrote in message news:%23GoI5tSDGHA.532[at]TK2MSFTNGP15.phx.gbl... - quote - > I have a recurring deposit set up each month for 14th. Now that this
Did you record the deposit in the register and not match it to the scheduled> deposit actually arrived at December 29th instead of next year's Jan 14th, > I've entered the next occurence (scheduled at Jan 14) into the register, > using Dec 29 date. > Everything is fine, BUT the budget for the Jan does not take this into > account. It still thinks there is going to be deposit at Jan 14 - even > thou it has been received earlier by Dec 29 and entered into the register. > Is it a known bug? I am usind Deluxe 2006 trial version. transaction? Is the scheduled transaction still in the bills list? |
|
#-1
| |||
| |||
| I have a recurring deposit set up each month for 14th. Now that this deposit actually arrived at December 29th instead of next year's Jan 14th, I've entered the next occurence (scheduled at Jan 14) into the register, using Dec 29 date. Everything is fine, BUT the budget for the Jan does not take this into account. It still thinks there is going to be deposit at Jan 14 - even thou it has been received earlier by Dec 29 and entered into the register. Is it a known bug? I am usind Deluxe 2006 trial version. -- Dmitry Korolyov [d__k[at]removethispart.mail.ru] MVP: Windows Server - Directory Services |
| Tags |
| bill or deposit, earlier, paid, problems, recurring |
Similar Threads | ||||
| Thread | Forum | Replies | Last Post | |
| Recurring deposit Ed: My bank shows "year to date interest" on their online account access screen. It seems that Money 2003 downloads this as a new transaction every time... | Microsoft Money | 1 | 02-22-2004 08:14 AM | |
| How do I enter a deposit that is not a recurring deposit? Don Stowell: How do I enter a deposit that is not a recurring deposit? | Microsoft Money | 1 | 09-29-2003 07:06 PM | |
| Recurring Deposit Glenn: Is there a way to make a recurring deposit on the 3rd Wed of each month? Social Security comes monthly, by that method rather than a specific date.... | Microsoft Money | 1 | 09-25-2003 05:19 AM | |
| Thread Tools | |
| Display Modes | |
| |