No. One must close the current database so that the library database is no
longer open and connected to any other database, then open the library
database, edit the code modules, and save the changes. Earlier versions of
Access had the same problem of faking that code changes to the library
modules were being saved from the current database VB Editor, so it's not
just Access 2003.