just brew it! wrote:
bthylafh wrote:Upgrade the database.
Preferably to something that doesn't have "Access" in its name, if you have the time and budget to do so.
Our programmer is slowly migrating this junk from Access to .NET+MSSQL. Still, got a lot of these things and he'd rather migrate to that than to Access 2000. Ah, and yeah, it's a custom VB/Access frontend that connects to an Access MDB. That was our internal application platform of choice back in, oh, 2000. Just upgrading a db, no sweat. It's all the forms and VB that's the problem.
However, he's got a ton of work already and this is a roadblock currently for migrating some users from XP to Win7. Being a roadblock it still isn't as important as the rest of the stuff he's working on and we don't have other programming resources. I know Access 2000 works fine in Win7 as some of our other stuff works on it just fine.
My options are to sludge through it myself, knowing nothing about VB or Access, or guilt him into doing it over a weekend or somethin'. I'm just glad we finally got everyone off of Access 2.0!