Help Needed With Bizarre Database Behaviour In Access 2003

[Wayne Aprato]

I have a simple database which was originally written in Access 97.
When converted to Access 2000 file format it ran flawlessly in Access
2002. I've just tried to run it in Access 2003 and I am seeing the
following behaviour:

Some of the fields on the continuous main form which is a list of jobs
with their related details "flicker". While this is going on the form
seems to function as it should and isn't locked up. If I click and
hold in any field the flickering stops until I release the mouse
button.

There are 3 fields in the form footer which sum the values of 3
related currency columns of fields. I tried removing these summed
fields but the behaviour continued. I then removed the control source
for a couple of fields in the form whose control source was a IIf
function which relied on values from some of the other fields. This
seemed to stop the "flickering". The only problem that remained was
that a field which sums 2 of the other fields won't show its value
until the mouse cursor is run over the column of text boxes. As the
mouse is run over each text box, it shows its value.

The above behaviour seems crazy but it must have a cause. As
previously stated this database runs flawlessly in Access 2002. The
mdb compiles with no problems.

Any help would be appreciated.

[Steve Jorgensen]

On 23 Feb 2004 01:45:19 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

I have a simple database which was originally written in Access 97.
When converted to Access 2000 file format it ran flawlessly in Access
2002. I've just tried to run it in Access 2003 and I am seeing the
following behaviour:

Some of the fields on the continuous main form which is a list of jobs
with their related details "flicker". While this is going on the form
seems to function as it should and isn't locked up. If I click and
hold in any field the flickering stops until I release the mouse
button.

There are 3 fields in the form footer which sum the values of 3
related currency columns of fields. I tried removing these summed
fields but the behaviour continued. I then removed the control source
for a couple of fields in the form whose control source was a IIf
function which relied on values from some of the other fields. This
seemed to stop the "flickering". The only problem that remained was
that a field which sums 2 of the other fields won't show its value
until the mouse cursor is run over the column of text boxes. As the
mouse is run over each text box, it shows its value.

The above behaviour seems crazy but it must have a cause. As
previously stated this database runs flawlessly in Access 2002. The
mdb compiles with no problems.

Any help would be appreciated.

Are you using conditional formatting? If so, this is a problem that occurs in
Access 2002 as well, and there's not much rhyme or reason as to when it does
and when it doesn't. Assuming it's the same bug, I wouldn't be surprised if a
random act such as opening it in 2003 instead of 2002 triggered the bug in
your particular case.

[Wayne Aprato]

Steve Jorgensen <no****@nospam.nospam> wrote in message news:<pf********************************@4ax.com>. ..

On 23 Feb 2004 01:45:19 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

I have a simple database which was originally written in Access 97.
When converted to Access 2000 file format it ran flawlessly in Access
2002. I've just tried to run it in Access 2003 and I am seeing the
following behaviour:

Some of the fields on the continuous main form which is a list of jobs
with their related details "flicker". While this is going on the form
seems to function as it should and isn't locked up. If I click and
hold in any field the flickering stops until I release the mouse
button.

There are 3 fields in the form footer which sum the values of 3
related currency columns of fields. I tried removing these summed
fields but the behaviour continued. I then removed the control source
for a couple of fields in the form whose control source was a IIf
function which relied on values from some of the other fields. This
seemed to stop the "flickering". The only problem that remained was
that a field which sums 2 of the other fields won't show its value
until the mouse cursor is run over the column of text boxes. As the
mouse is run over each text box, it shows its value.

The above behaviour seems crazy but it must have a cause. As
previously stated this database runs flawlessly in Access 2002. The
mdb compiles with no problems.

Any help would be appreciated.

Are you using conditional formatting? If so, this is a problem that occurs in
Access 2002 as well, and there's not much rhyme or reason as to when it does
and when it doesn't. Assuming it's the same bug, I wouldn't be surprised if a
random act such as opening it in 2003 instead of 2002 triggered the bug in
your particular case.

Thanks Steve. I had the text in all fields formatted conditionally
and this was obviously more than Access could take. I removed this and
the problem disappeared. I still have the background colour of a
couple of fields formatted conditionally, but this doesn't seem to be
causing a problem. In your experience, is the problem more likely to
appear when a large number of fields is formatted conditionally as was
my case, or is it random? Conditional formatting is a handy feature,
but I won't be using it if it causes reliability problems.

Regards.

[Steve Jorgensen]

On 23 Feb 2004 12:52:17 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

Steve Jorgensen <no****@nospam.nospam> wrote in message news:<pf********************************@4ax.com>. ..

On 23 Feb 2004 01:45:19 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

>I have a simple database which was originally written in Access 97.
>When converted to Access 2000 file format it ran flawlessly in Access
>2002. I've just tried to run it in Access 2003 and I am seeing the
>following behaviour:
>
>Some of the fields on the continuous main form which is a list of jobs
>with their related details "flicker". While this is going on the form
>seems to function as it should and isn't locked up. If I click and
>hold in any field the flickering stops until I release the mouse
>button.
>
>There are 3 fields in the form footer which sum the values of 3
>related currency columns of fields. I tried removing these summed
>fields but the behaviour continued. I then removed the control source
>for a couple of fields in the form whose control source was a IIf
>function which relied on values from some of the other fields. This
>seemed to stop the "flickering". The only problem that remained was
>that a field which sums 2 of the other fields won't show its value
>until the mouse cursor is run over the column of text boxes. As the
>mouse is run over each text box, it shows its value.
>
>The above behaviour seems crazy but it must have a cause. As
>previously stated this database runs flawlessly in Access 2002. The
>mdb compiles with no problems.
>
>Any help would be appreciated.

Are you using conditional formatting? If so, this is a problem that occurs in
Access 2002 as well, and there's not much rhyme or reason as to when it does
and when it doesn't. Assuming it's the same bug, I wouldn't be surprised if a
random act such as opening it in 2003 instead of 2002 triggered the bug in
your particular case.

Thanks Steve. I had the text in all fields formatted conditionally
and this was obviously more than Access could take. I removed this and
the problem disappeared. I still have the background colour of a
couple of fields formatted conditionally, but this doesn't seem to be
causing a problem. In your experience, is the problem more likely to
appear when a large number of fields is formatted conditionally as was
my case, or is it random? Conditional formatting is a handy feature,
but I won't be using it if it causes reliability problems.

Regards.

The only things I know make it more likely is when you combine calculated
controls and conditional formatting and/or when you have other controls
overlaying conditionally formatted controls such as when you try to use a
conditionally formatted control as a background. Also, in Access 2002, I find
that Locked/Disabled does not behave properly wiht conditionally formatted
controls. The user is allowed to set the focus to it by clicking, though the
Disabled flag is supposed to prevent this.

[Wayne Aprato]

Steve Jorgensen <no****@nospam.nospam> wrote in message news:<k2********************************@4ax.com>. ..

On 23 Feb 2004 12:52:17 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

Steve Jorgensen <no****@nospam.nospam> wrote in message news:<pf********************************@4ax.com>. ..

On 23 Feb 2004 01:45:19 -0800, cq*******@volcanomail.com (Wayne Aprato) wrote:

>I have a simple database which was originally written in Access 97.
>When converted to Access 2000 file format it ran flawlessly in Access
>2002. I've just tried to run it in Access 2003 and I am seeing the
>following behaviour:
>
>Some of the fields on the continuous main form which is a list of jobs
>with their related details "flicker". While this is going on the form
>seems to function as it should and isn't locked up. If I click and
>hold in any field the flickering stops until I release the mouse
>button.
>
>There are 3 fields in the form footer which sum the values of 3
>related currency columns of fields. I tried removing these summed
>fields but the behaviour continued. I then removed the control source
>for a couple of fields in the form whose control source was a IIf
>function which relied on values from some of the other fields. This
>seemed to stop the "flickering". The only problem that remained was
>that a field which sums 2 of the other fields won't show its value
>until the mouse cursor is run over the column of text boxes. As the
>mouse is run over each text box, it shows its value.
>
>The above behaviour seems crazy but it must have a cause. As
>previously stated this database runs flawlessly in Access 2002. The
>mdb compiles with no problems.
>
>Any help would be appreciated.

Are you using conditional formatting? If so, this is a problem that occurs in
Access 2002 as well, and there's not much rhyme or reason as to when it does
and when it doesn't. Assuming it's the same bug, I wouldn't be surprised if a
random act such as opening it in 2003 instead of 2002 triggered the bug in
your particular case.

Thanks Steve. I had the text in all fields formatted conditionally
and this was obviously more than Access could take. I removed this and
the problem disappeared. I still have the background colour of a
couple of fields formatted conditionally, but this doesn't seem to be
causing a problem. In your experience, is the problem more likely to
appear when a large number of fields is formatted conditionally as was
my case, or is it random? Conditional formatting is a handy feature,
but I won't be using it if it causes reliability problems.

Regards.

The only things I know make it more likely is when you combine calculated
controls and conditional formatting and/or when you have other controls
overlaying conditionally formatted controls such as when you try to use a
conditionally formatted control as a background. Also, in Access 2002, I find
that Locked/Disabled does not behave properly wiht conditionally formatted
controls. The user is allowed to set the focus to it by clicking, though the
Disabled flag is supposed to prevent this.

I had both - calculated controls that were conditionally formatted and
other controls overlaying them that became visible under certain
conditions. The locked/disabled behaviour is a good one to keep in
mind as well.

Regards.