Moving a Scoutwest Standard Time database off MS Vista

Posted by Robert Merrill on February 11, 2011 under Tech Tips | Be the First to Comment

I couldn’t find a Scoutwest Standard Time forum, and there were no entries for it on Experts Exchange, so that’s why this solution is in this obscure place.

When moving a Standard Time database from Microsoft Vista, it may not be where you think it is. The Scoutwest documentation for, “How do I move an ODBC database to a new place?” says, “1. Copy Standard Time.mdb to the new directory or a new machine.” Simple enough. The File DSN definition says it’s in C:\Program Files\Standard Time, and sure enough, there’s a file there named Standard Time.mdb. But that might not be the one you want.

If you bring that file over to, say Standard Time 7 on Windows 7, you’ll put it in C:\Users\<username>\Documents\Standard Time\Standard Time.mdb. That’s where my fresh install of ST v7 created its empty database, behind a File DSN still called Standard Time mdb (no period) as in v4. But of my four years of client billable hours records—nothing.

At first I attributed it to the upgrade process, going from v4 on the Vista machine to v7 on the 64-bit Windows 7. The very helpful Scoutwest rep didn’t think so, but let me download v5 and v6 to run the upgrade one step at a time. I did that on the Vista machine and it worked flawlessly. Now that I had a v7 database, I thought, “Bob’s my uncle,” as they say.

But still no joy. I made a copy of the database in C:\Program Files\Standard Time on the Vista machine and inspected it with Access 2007 (.mdb is the old Access JET format, but 2007 can still work with them). No upgrade records in the Version table. Huh. Plus, it’s awfully small—827K. But yet I start Standard Time 7 on the old machine and there it all is.

Finally, a full-system search revealed the copy lurking in C:\Users\<username>\AppData\Virtual Store\Program Files\Standard Time—a v7 Standard Time.mdb of over 30 MB, complete with four records in Version. I copied that file to the Windows 7 machine and all was well.

Just to prove my hypothesis, I restored the v4 database to AppData\Virtual Store from backup and copied that to Windows 7. Standard Time v7 did the upgrade in place, and there were the last four years of my business data.

Standard Time’s a great product for anyone who has to keep accurate records of their time. But if you’re running into trouble getting those records off of a Windows Vista machine, maybe this will help you.


Posted by Robert Merrill on February 10, 2011 under Concepts, uFunctional Values | Be the First to Comment

I’m too old for pink sunshine, so let’s just get it out there, even in front of potential clients. Not everybody likes me, or the way I go about things.

When this dislike comes out, it usually contains the word “academic.” Read more of this article »