<?xml version="1.0" encoding="utf-8"?>
<!-- RSS generated by Web Crossing(r) Unix-v6.0 built Aug  7 2008 14:23:09 (source:1141 2008-08-07 14:01:13 -0700)/-6.0 on 2010-03-21-05.33.18 GMT -->
<rss version="2.0">
<channel>
<title>Quicken Community: Mileage</title>
<link>http://www.quickencommunity.com/webx/.efde012</link>
<description>
QMEM V2 and now V2.1 do something funny (not so funny).  If you enter, in this order: &lt;br&gt;&lt;br&gt;1- a provider (but no mileage for that provider), 2- add a visit &lt;br&gt;
3- update the provider with the roundtrip mileage &lt;br&gt;&lt;br&gt;that visit will forever show 0 miles in the tax report, rather than accepting the updated miles. &lt;br&gt;&lt;br&gt;I can see only one positive use for this strange behavior...when a provider moves from one location to another.  Then you can enter mileage 1, update it to mileage 2, and visits at location 1 will be calculated with mileage 1 and visits to location 2 will be calculated with mileage 2. &lt;br&gt;&lt;br&gt;But this behavior means I must manually update the mileage for each individual visit when I learn of the mileage after entering visits...</description>
<lastBuildDate>Thu, 19 Apr 2007 20:04:11 GMT</lastBuildDate>
<generator>Web Crossing(r) Unix-v6.0 built Aug  7 2008 14:23:09 (source:1141 2008-08-07 14:01:13 -0700)/Unix-6.0 (http://webcrossing.com/)</generator>
<docs>http://backend.userland.com/rss</docs>
</channel>
</rss>
