A little quirk

[bozzer]

When I start a trip I enter my starting mileage. Vehicle Manager assumes an end odemeter reading. When I am finished for my trip, I enter the real ending mileage. What I am finding however, is that when I now select a new trip after that, it starts with the assumed ending milage, instead of the real mileage I recorded. When I go into manage the vehicle, it is not showing that new milage I recorded, rather the assumed mileage it entered when I first started the trip.

[michael]

Hi bozzer,
I'm not able to reproduce this. Each new Trip I have entered trying to test this, showed the adjusted odometer ending mileage from the previous trip +100 miles.

Though you didn't indicate if you're using the SmartPhone edition or PocketPC edition, I tried on both, and got the same behavior for both.

Can you please go to Menu->About and tell me what version/build you have installed? Thanks.

[bozzer]

Hii Michael,

I am using version 3.3 build 104. What seems to happen is that when I enter the starting mileage, yes it adds 100. but if my ending mileage is only 50 miles, and I make the adjustment to the ending mileage, when I start a new trip, it shows me the 100 mile adition, not the 50.

so my exampe: Today i started my mileage at 84446. It automatically ended at 84546. My trip was only 22 miles so when I adjusted the end mileage to 84468, and went to start a new trip, it started at the 84546, not the 84468.

I am using a Sprint Treo 700wx.

I also notice that it is the milage on the main vehicle screen that is not accurate. I added some test data and as I add new trips I have to manually put in both beginning and ending mileage becase the system does not seem to remember last entries.

[michael]

See the screenshots. Am I missing something?

[bozzer]

See the screenshots. Am I missing something?

As your thumbnails have it, that is what i see. The problem is, on day 2 if I change the end to something less than the 568, to let's say 525 miles, and start a trip 3, it will show the 568, not the 525

[michael]

But I didn't get that. If I change the end #2 to 84525, then start a 3rd trip, the 3rd trip shows Start: 84525 and End: 84625.

So unless I'm misunderstanding, it's retaining the ending mileage from the previous trip and showing this value as the start mileage for the next trip.

[bozzer]

for some reason that is not happening on mine. don't know what the issue is, but it doesn't seem to adjust and reset to the correct mileage as I explained in previous messages. I even tried to set up some tests but the same thing happens. should i try to reinstall?

[michael]

I wouldn't reinstall. Can you instead try creating/using a different .dat file. You can keep your existing one, but just move it somewhere safe, then launch VM, and it will tell you that you need to create a new one.

[bozzer]

Michael,

Not being that technical, I do not know where the .dat file is on my Treo. I did find a VehicleML file, but I can't seem to do anything with it.

In further investigation, the issue arises when the mileage is saved and I go back in to edit, and it saves the old mileage, not the edited version

[michael]

bozzer,
I apologize for not clarifying the steps. The .dat file is (by default) in My Documents on your device. This may not be true if you selected a different location upon initial installation.\

Also you will not be able to see the .dat extension. The file you're looking for should be named MyVehicles. Unless of course, like above you named it something different upon initial installation. If this is the case, it will be called whatever you named it.

To access it simply launch File Explorer on your device and navigate to My Documents, and scroll the list until you locate it.

1. Then go to Menu->Edit>Cut.
2. Next, navigate to another folder of your choice (one you can remember) and go to Menu->Edit->Paste.
3. Now relaunch VM, and you should be prompted to create a new profile

You can always go back to your original data file by reversing these steps

[bozzer]

Michael,

thanks for the directions but it seems when it was installed it only put the cab file in my documents. I did not change paths or names just let it install where it wanted to . so I will have to do a seach now that I know the name.

[RTMcFadden]

I have the same problem. Using version 3.2, on a Dell Axim x51v with WM 5. Whenever I create a new extry, it takes the intial ending value from the previously created entry. That is to say, the value when first saved. If I let the default value to milage+100 when intitally saving that value, that is what is displayed on the creation of the next entry. Regardless of me changing the ending value later. As a matter of fact, it will not release the milage+100 value until I suprass it. On several instance, I have created multiple entries with the milage differential set to 0, and the starting and ending values were less than the original milage+100 and whenever I create a new entry, it starts at that original milage+100. Since then, the only way I have been able to prevent this from happening is to set the starting and ending milage to the same value. Unfortunatley, there is no way to set a default value for the elapesed milage.

[Roko000]

I'm sorry, I don't understand

[Krypton217]

I am currently using Cingular 8525 and everytime I go to enter a new trip it automatically inputs the mileage that is in the My Vehicles window.
Name: Acura Mileage
Year: 2003
Odometer: 46800

Whenever I enter a new trip it automatically defaults the beginning mileage as 46800.

[Hookey]

I have also problem in entering the start of my trips. It always suggests
1 330 300 km as a start, a value that is not even valid, since my odometer is now at 134 878 km. I might sometime have entered the wrong (1 330 300) value (there is a '0' to much in the end, I guess... ) but now that value is not present in the database.. it is anoying this... I hope it is supposed to show the last recorded odometer ending, as the default odomoeter start of next trip?

regards, Hakan

[Krypton217]

It would just make sense that it would use the last mileage enter as the starting mileage. I am dissapointed that I did not pick this up in the demo version.

[bozzer]

As I understand it, they are working on the fix.

[Hookey]

Hi Iambic team, it would be very nice if you answered the questions about this problem, which seems to be a general one. I suggest that if you once have entrered a value that is higher than "any other" value, the porgram uses this value as default start value- Some one else said something about the program using this value until it was passed in som otehr entry. I thin this "highest" value of them all wrongly is saved instead of the last recorded end-value.