, Blue Ink wrote

@figuerres: +1

The only problem I see is that mdb files don't play nicely with .NET nowadays. Switching to a different solution (such as SQL Server Compact, for instance) can be a life saver in some case.

the OP also mentioned SQL 2000 and i would have them look at at the least upgrading to SQL 2008 or 2012 if they want to stay with the Microsoft servers.....