Access 2007 Conversion Problem

[Pj Paquette]

I have an application that works fine in Access 2003 but has some weird
display issues in Access 2007. I have applied the latest software pack
upgrades. I have tried my 2003 mde in 2007 and tried the mdb in 2007 and get
the same resulkts.

#1 - A dropdown box is shown on a subform with several following fields.
Usable fields are in white and the background is blue. When a dropdown box
is selcted, the list of values is displayed which overlays on top of the
subseuent fields (expected). However, after the list box is closed, the area
that was overlayed on the following fields now shows up as the background
blue rather than white. THe form being affected is a subform.

#2 - When a form window is opened (the form has sub forms and tabs), the
form is constantly being refreshed (constant flickering of the mouse and
parts of the form). A field on a subform was flickering (with each refresh)
- I physically exchanged the field with another on th form and now the new
field is flickering - no code was changed. THe field affected is a dropdown
although no effect was seen on other dropdowns in the same form/subform.

Help. I would like to get this resolved but I do not have a clue as to
where to start looking for an answer. An answr or guidance would be
appreciated. Thanks.

 

[Jeanette Cunningham]

1#
the usual fix for combo display problems in A2007 is to set the alternate
back color of the combo to any color, make sure it has a color.

2#

 

[Jeanette Cunningham]

the last post sent before I had time to check and correct it.
I just discovered that if I press Ctl+Enter in outlook express, my reply is
sent straight away.

1#
the usual fix for combo display problems in A2007 is to set the alternate
back color of the details section to any color, make sure it has a color.

2#

The flickering seems to be related to the specific type of code you write.
Usually it is some code that makes access go back to the table or query and
fetch the data again.

One thing you can try is to use
DoCmd.Echo False
at the start of any code that sets or changes a record source

Be very careful to use
DoCmd.Echo True
in the on exit part of your error handler, or just before the end sub or end
function if you do not have an error handler.



Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Pj Paquette]

1#

the usual fix for combo display problems in A2007 is to set the alternate
back color of the details section to any color, make sure it has a color.

Tried this and it worked.

2#

The flickering seems to be related to the specific type of code you write.
Usually it is some code that makes access go back to the table or query and
fetch the data again.

I do not have any code that refreshes or repaints the window. So, I will
check into what you suggest and see if I can isolate the problem code.

 

[Pj Paquette]

Sorry, tthanks for the assistance.

 

[Jeanette Cunningham]

Look for any text boxes that are visible and for their control source have
an expression (it will start with an equals sign).
Temporarily hide these to see if that makes a difference.

You can see if there is any difference when you turn off access themed
controls, or if there is any difference when the tab control is set to
transparent or not.

You can also put a break point on the current event for your form and watch
what happens as the form opens to see if there is something there that
triggers the constant refreshing.

Next, comment out as much code as possible until the flickering stops, then
one by one, uncomment subs and functions until you find what causes the
constant refreshing.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[Pj Paquette]

Jeanette

I have tracked down the offending statement.
" Forms!frmIncidents!lstActivity.RowSource = gblActivitySQL & Me!IncidentRK
& gblActivitySort" which translates into "SELECT * FROM qryActivity WHERE
IncidentFK = 1 ORDER BY ActivityRK"

The statement sets the rowsource for a record list construct. This should
not be a problem. If I execute, it basically keeps repeating the section of
code that contains this statement forever; however, if I put a statement
trace on the code section, it only executes the code section once. Do you
have any suggestions?

 

[Pj Paquette]

As noted in previous reply, found the statement; however, problem occurs when
tracing is off; does not occur when tracing is on

 

[Jeanette Cunningham]

Where are you calling the code that sets that row source?
You could try the DoCmd.Echo False at the start of the code that calls the
row source and remember to off echo at the end of that code.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[AG]

Jeanette,

I hadn't previously seen anything on the alternate back color property for a
combo box, and can't find any references to it via Google search. How does
one set it?

 

[Jeanette Cunningham]

For the detail section of a form there is the alternate back color property
which can affect the visibility of a combo.

Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[AG]

Jeanette,

Thanks for the reply.
I see how the detail section alternate back color affects continuous forms,
but I can't get it to have any effect on a combo box.
Is there some other property that must be set also?

 

[Jeanette Cunningham]

It can have an effect on combos. If the alternate back color is set to,
(from memory it is No Color)
then there can be issues with combo dropping down but the data in the list
is not visible.
The work around is to make sure that the alternate back color is set a
particular color, doesn't matter which one.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

 

[AG]

Thanks Jeanette,

I guess I misunderstood. I don't have a problem with the combos dropping.
When I saw 'alternate back color' and 'effect on combo', I thought it might
make the combo list display with alternate colors.