tag:infinitekind.tenderapp.com,2009-01-14:/discussions/problems/58769-datesInfinite Kind: Discussion 2020-04-22T15:00:24Ztag:infinitekind.tenderapp.com,2009-01-14:Comment/480270832020-01-22T14:53:22Z2020-01-22T15:14:15ZDates<div><p>There can be as many as four dates for the same online transaction in Moneydance:</p>
<ol>
<li>The date that Moneydance suggests for the online transaction.<br></li>
<li>The date that the user inputs for the transaction<br></li>
<li>The date that Moneydance enters into the register for the transaction, which does not match either #1 or #2, and which Moneydance seems to choose at random.<br>
4 .The date listed in the online payment outbox.</li>
</ol>
<p>The date in #4 always agrees with the date in #2. Moneydance knows the correct date, because it is in the Outbox. Why can't Moneydance ask itself for the date in the outbox and enter it in the register? The dates in #2, #3, and #4 should always be the same. No exceptions.</p>
<p>At present, making an online transaction is a three step process:</p>
<p>a. Enter a date for the transaction in the dialog box.<br>
b. Check the date in the outbox<br>
c. Correct the date in the register to match the date in the outbox.</p>
<p>WHY? There should be only one step. Moneydance should never record an incorrect date in the register. Moneydance has an option for specifying an interval for the suggested transaction, but that only scrambles the register.</p>
<p>I HAVE REPORTED THIS PROBLEM SEVERAL TIMES OVER THE LAST FEW YEARS, AND EACH TIME YOU CLOSED IT WITHOUT RESPONDING, COMMENTING, OR FIXING THE PROBLEM.</p></div>Ken