> I have been tasked with migrating data from a large MS-Access DB to a
MS Access is a filesystem database. It is fundamentally different from a
server database. Although access can mimic a server by sending SQL to
itself and then parsing it again, this is off course not very nice in
If the forms are built with linked tables, the performance is probably
not an issue anyway.
I would not call switching from your own car to using public transport
"upsizing", even though buses are bigger. Using MySQL or SQL Server is a
matter of taste and experience (and money).
For the migration, you can download MyODBC (for MySQL) and link the
MySQL tables in Access. This is probably not the fastest way, but it is
easy and gives you all the control you need, without having to switch to
using new programs. And if you haven't heard of "pass-through" queries
yet, read the MS Access helpfile on them.
I can't estimate the time it takes you to set up a server and to learn
to work with it. After that, the estimate is even more difficult: do the
access forms still perform sufficiently? Should that be part the migration?