I recently deployed a major new version of our complex Access app, and most
of it went off without a hitch except for one oddity...

One of the primary forms has tabs containing several sub-forms (one each)
with a Continuous Form inside. The sub-forms have conditional formatting
installed so they become enabled=false if the row has a certain value set,
specifically "isManual=0". Additionally there is an override, in code, that
forces _everything_ to enabled=false if the master record is in a certain
state (isDeleted=1).

This all works well on my machine. It doesn't work so well on about half of
the other machines, leaving the form disabled. I've been trying to find out
why for the last couple of hours, but no luck so far.

So I'm curious about version issues. Are there any known issues re-enabling
form fields in code in certain versions? I installed 2003SP2 on one afflicted
machine, to no effect. My machine's version ends in .8132, but even after
installing SP2 on the other machine it says .6360. Does anyone know where I
could get the .8132 version to see if that's the problem?

Maury

After the latest MS Office update my Access 2003 forms have some issues with
conditional formatting. On some forms some of the conditions work and some
do not. Deleting the condition and recreating it seems to solve the problem.
Not sure why I have to go through 100s of forms and check all conditions and
then recreate some of them and then reissue them to dozens of clients.
Another case of MS broke it.
Alex

"Maury Markowitz" <(E-Mail Removed)> wrote in
message news:28E11846-8183-4E0E-93F7-(E-Mail Removed)...
>I recently deployed a major new version of our complex Access app, and most
> of it went off without a hitch except for one oddity...
>
> One of the primary forms has tabs containing several sub-forms (one each)
> with a Continuous Form inside. The sub-forms have conditional formatting
> installed so they become enabled=false if the row has a certain value set,
> specifically "isManual=0". Additionally there is an override, in code,
> that
> forces _everything_ to enabled=false if the master record is in a certain
> state (isDeleted=1).
>
> This all works well on my machine. It doesn't work so well on about half
> of
> the other machines, leaving the form disabled. I've been trying to find
> out
> why for the last couple of hours, but no luck so far.
>
> So I'm curious about version issues. Are there any known issues
> re-enabling
> form fields in code in certain versions? I installed 2003SP2 on one
> afflicted
> machine, to no effect. My machine's version ends in .8132, but even after
> installing SP2 on the other machine it says .6360. Does anyone know where
> I
> could get the .8132 version to see if that's the problem?
>
> Maury
>

"paradigm" wrote:

> Another case of MS broke it.

lol! Well at least I'm not going crazy...

Maury

paradigm wrote:
> After the latest MS Office update my Access 2003 forms have some issues
> with conditional formatting.

Look at the bright side. At least you get to choose your SP level and,
correspondingly, which set of capabilities and bugs you want to deal
with :-). I'm telling everyone in the office to avoid SP3 for A2K3.

James A. Fortune
(E-Mail Removed)