How about migrating jet (red) to jet (blue)... and...
... and remove the 2 Gb size limitation?
oh, and currently, under office 2007, I can't even access data tables by default due to security settings!
the problem is that as Access *is* a programming platform, along with all office documents, and that access has an 'autoexec' function, the only way you could stop malicious code being executed is to:
1) remove the VBA environment, and ship it as a stand alone module: 1 database, 1 VBA project. An access linked project cannot run until it has both database and project available. Having the user load both independant units would mean that the luser is really asking for it ;)
2) Hardcode a VBA check to refuse to launch any VBA code if the document root is in any temp/tmp/temporary internet files directory: the VBA environment would only work after saving the project to the hard drive then launching it.
Mix both, and you would have to save both docs to the main file system, and execute the project. Running (or autorunning through a security hole in browser/email client) would fail due to the temp dirs being no execute: you should only be able to read data, but nothing should be executed from there.
This would stop other Office documents working as a "dropper", i.e. opening from temp, execing autoexec, dropping another document and executing that with all local rights, getting round any gateway filtering (temporarily anyway) that may be used.
Taking this a little further, it would really be nice if MS could even mark all Temp/tmp/temporary internet files folders with some sort if NOEXEC flag: not only would it stop this sort of thing (though you could get around this with some crafty social engineering), but would also stop a very large part of internet browser mamlware/spyware/virus installs that generally tend to run from those same temp directories...