Access Macros & the property "Visible"

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Okay, I have a problem that may or may not be simple, so hopefully somebody
can help me out. I am helping some coworkers with a problem with their
custom database application. The person who originally made this
application has passed away and now they are having problems with it now that
they have upgraded from Access 2002 to Access 2005. I offered to help them
out, but this is out of my league.

The majority of their problems come from a macro not functioning.
Whenever I run a button/process that uses that macro, I get the following
message: "You entered an expression that has an invalid reference to the
property 'Visible'. The property may not exist or may not apply to the
object you specified." I can only then halt the procedure. When I run
this process on an older (Access 2002) version, it works fine. The later
versions have problems. When I look at the macro design, everything looks
the same as far as conditions are established, etc. So, it appears the
problems are not just "skin deep".

I am not a programmer at all - I know my way around Access enough to handle
my needs. If anybody can provide a solution or a step in the right
direction, I would appreciate it.

Thanks,

John
 
ACCESS 2005 isn't a product -- I assume you mean 2003 < g >

There is/was a "bug" in ACCESS 2003 re: macro's SetValue action. See this
Microsoft Knowledge Base article for
more information and how to work around it:

Microsoft Knowledge Base Artilce 841916
You may receive an error message when you run a macro that uses the SetValue
action to set the Visible property of an object in Access 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;841916
 
Sorry about the product screwup - one machine is running Access 2003, and
another is running Office XP. I guess I got confused, but don't know how I
came up with Access 2005.

Thanks for the tip/pointer on the SetValue. I will try to put it into the
application here, and hopefully not cause bigger problems.

I do have one problem - when I look at the large macro that is used (all of
the analysis report/functions call up this macro), I see the original
developer has designed it with multiple "stages". For instance, on a parts
analysis, the push button only "points to" or "activates" a small section of
the macro. Do I need to modifty the steps of every small section of the big
macro to call into play the new part I add in (the SetVisible macro)?

Again, since I'm not a programmer, I'm a little "trigger-shy" on doing these
types of programming changes. I need to fix the problems without causing
more catostrophic ones.

Thanks,

John
 
I'm not sure I understand what you mean by "stages"? Do you mean that there
are many macros in a single macro object (each macro gets its own name in
the Macro Name column)?

I recommend that you will need to make the change everywhere the macro(s)
use the SetValue property to change the Visible property of an object.

--

Ken Snell
<MS ACCESS MVP>
 
Back
Top