Clients with Access 2003 can't use my database because macros are
blocked.  At a colleagues recommendation, I went into Tools, Macros,
Security, and changed the level from Medium to Low.  The macros then
worked properly, but when they tried to close the database, they were
warned that the file had become corrupted.  This happened twice, so we
returned the level to Medium.

Is there a fix for this?  Some clients with 2003 have no trouble;
others can't use the database, but I can't figure out why.  Any help
would be greatly appreciated.  TL

On Nov 4, 9:14 pm, Chuck Grimsby <cgat... at (no spam) gmail.com> wrote:

On Nov 4, 1:07 pm, Tomahawk Lady <nancycmarsh... at (no spam) verizon.net> wrote:

Clients with Access 2003 can't use my database because macros are
blocked.  At a colleagues recommendation, I went into Tools, Macros,
Security, and changed the level from Medium to Low.  The macros then
worked properly, but when they tried to close the database, they were
warned that the file had become corrupted.  This happened twice, so we
returned the level to Medium.

Is there a fix for this?  Some clients with 2003 have no trouble;
others can't use the database, but I can't figure out why.  Any help
would be greatly appreciated.  TL

Have you tried digitally signing your code?

I went to Microsoft Training and learned how to create a digital
signature. Then I went to the home of a user who cannot run my
program, created a digital signature, signed the program, declared it
to be a trusted publisher, but it still won't work.  This program runs
successfully on Access 2000, 2002, 2007, and at least 6 computers with
2003.  However, 2 users with 2003 can't use it.  Help!

But, Chuck, back to your email questions. . .I do compile my database,
but I've never heard of decompiling, so, no, I haven't tried that.

Tony, The only VBA code I use is a DROPDOWN to open combo boxes.
Otherwise I stick to queries and macros. I Compact On Close in all my
programs. Decompile seems to be targeted at VBA code; would it really
help me?