For the most part, it works, but there are a few things that aren't working right - for example, the 2nd-gen Honda Civic Hybrid category.
In order to fix these issues and make the software & database easy to maintain, it will be necessary to overhaul it. To be more specific, we will be rewriting it from scratch. We don't have developer resources to devote to this task at the moment, but it's in the queue and we expect to begin work within the next few months.
The data currently in the database will be imported when we do the switch, so we don't expect to lose any information. The application will work the same way (or mostly the same way) that it does now.
IMHO, a chance to remove some of the "noise" if resources permit.
Suggestion: Add a field for the last entry date, and remove all entries over 90 days or so without an update that have less than a meaningfull number of tanks (say 10 or so, at least). This will remove the fast-starters that don't stick with a program and leave first tank distortions, newbie claims, etc. in the data.
Perhaps change the screen print color for cars that are inactive. (Over the minimum tanks, but no update in the 90 day or so time period.
It is the ignorant among us that will eventually destroy us all.
We've got a working prototype. I don't have an ETA for when we'll have the final version rolled out here, but it's being actively worked on. The make/model/trim/etc will be populated automatically from a central data source, so as soon as we know about a new model, it'll be available.
Yes, what's the deal with the update to the milage db? I appreciate improvements being made, but greenhybrid are about to dilute or destroy their greatest asset. A few days more without being able to log data and people will stop reporting.
Why does the db has to be closed for reporting while the improvements are being made? Couldn't the old version be available until the new one is ready to be launched?