After Upgrade From 2002 TO 2003 Security Option Under Macros Is NoLonger There?

[Barbara Schneier]

After upgrading from Access 2002 to Access 2003 the Security option
under Tools Menu, Macros has disappeared. I tried repair and then
reinstall, but that did no good. While I was reinstalling I got an
Error 1919 Error that stated "Configuring ODBC data source: MS Access
Database, ODBC Error 6. Component not found in the registry. Verify
that the file MS Access Database exists and that you can access it.

The only problem I am having is that when I click to open a database a
Box comes up Titled Security Warning and states: "This file may not be
safe if it contains code that was intended to harm your computer. Do you
want to open this file." Then it give the option to Cancel or Open the
file. Any help would be appreciated in getting back the Security option
under Macros. Thanks.

 

[B. Schneier]

After upgrading from Access 2002 to Access 2003 the Security option
under Tools Menu, Macros has disappeared. I tried repair and then
reinstall, but that did no good. While I was reinstalling I got an
Error 1919 Error that stated "Configuring ODBC data source: MS Access
Database, ODBC Error 6. Component not found in the registry. Verify
that the file MS Access Database exists and that you can access it.

The only problem I am having is that when I click to open a database a
Box comes up Titled Security Warning and states: "This file may not be
safe if it contains code that was intended to harm your computer. Do you
want to open this file." Then it give the option to Cancel or Open the
file. Any help would be appreciated in getting back the Security option
under Macros. Thanks.

Please disregard the above. After sending my message I continued to
look in the Newsgroup and finally found a post that described my "No
Security Option" problem and how to fix it by going to customize and
adding Security to the Macros options on the the Tools Menu. I tried it
and it worked.

 

[kruth]

I had the same problem and just found the solution in
knowldege article 833219. It's a known bug.