G
Guest
I recently started using Access 2003, moving up from Access 97. The one new
behaviour which I dont care for is its prohibition of saving codes stored in
a referenced library. For instance, if I open a module in the local database
which has a function call to a procedure stored in an referenced library, it
allows me to goto to the definition of that external procedure and change the
coding. However, it doesnt allow me to save the changes. While that may be
intuitive for some, it doesnt quite do it for me. Having to close the local
database, open the library, and open the module that has that procedure in
order to make the changes all over again seems to me to be a step backward
from what Access 97 allowed.
Also, if you attempt to open a library database while a client databsase of
that library is open, Access throws an error dialog and crashes.
Are these behaviours customizable? If so, how do I configure them?
Thanks
behaviour which I dont care for is its prohibition of saving codes stored in
a referenced library. For instance, if I open a module in the local database
which has a function call to a procedure stored in an referenced library, it
allows me to goto to the definition of that external procedure and change the
coding. However, it doesnt allow me to save the changes. While that may be
intuitive for some, it doesnt quite do it for me. Having to close the local
database, open the library, and open the module that has that procedure in
order to make the changes all over again seems to me to be a step backward
from what Access 97 allowed.
Also, if you attempt to open a library database while a client databsase of
that library is open, Access throws an error dialog and crashes.
Are these behaviours customizable? If so, how do I configure them?
Thanks