Hi, Paul.

A custom command bar is an Access-specific object, so its properties are
saved in the monolithic record with all the other database application
objects, such as forms and reports.  The user needs an exclusive lock on the
Access 2K (or later) database in order to make design changes, either
manually or through VBA code, to any of these Access-specific objects.  This
prevents database file corruption.

This feature was not available in Access 97 and earlier versions of Access,
so databases in a multiuser environment undergoing design changes to objects
like a form while another user was using that form often caused corruption.
This exclusive lock requirement in Jet 4.0 databases prevents the
corruption.

One can avoid this problem by splitting the database application into a
front end and a back end.  The back end, which contains the tables and
relationships, would reside on a shared network server.  A copy of the front
end, which contains all of the forms, queries, reports, macros, and modules,
would be placed on each user's workstation, with links to each of the tables
in the back end database file on the server.  Since each user would be
changing the command bar caption in a database file that no one else is
sharing, error #3734 would not occur.

For more information on split databases, please see the "Split the Database"
tip on this Web
page:

http://www.Access.QBuilt.com/html/gem_tips.html

One can also make the caption on the command bar's button permanent, and
this error will not occur whenever other users are also in the database,
since no design change would be made.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)