G
Guest
Good day all...
I'm having a rather strange thing happen to my Access application. I have a
process that when it finishes, leaves the database window up, but the buttons
do not show until I mouse over them. In addition, there is a form open, but I
can not view it. None of the object type buttons on the left side of the
screen (tables, queries, forms....) are visible either, whether I mouse over
them or not. The menus only show on mouse over too. I have tried using the
refreshdatabasewindow method in VBA, but it just repaints it just like
before, with the same issues. I have minimized the window and re-maximized
with no effect. If I shut the db down and re-open, the view is normal again.
The VBA editor window appears to be unaffected, although, at times, the
normal toolbars and menu disappears, but this is only an issue at design time
and I can live with it if I could fix my primary issue. The process that I
ran and left the db window in this state references Microsoft CDO For
Exchange 2000 Library, Microsoft ActiveX Data Objects 2.x, as well as DAO
recordsets and a few createobject (Excel.application).
All recordsets are being released, all instances of excel are being killed,
and the variables are set to nothing at the end of the process. I have
stepped thru the code a line at a time and all operate as expected, but leave
the UI in the aforementioned state. Am I going insane??
I'm having a rather strange thing happen to my Access application. I have a
process that when it finishes, leaves the database window up, but the buttons
do not show until I mouse over them. In addition, there is a form open, but I
can not view it. None of the object type buttons on the left side of the
screen (tables, queries, forms....) are visible either, whether I mouse over
them or not. The menus only show on mouse over too. I have tried using the
refreshdatabasewindow method in VBA, but it just repaints it just like
before, with the same issues. I have minimized the window and re-maximized
with no effect. If I shut the db down and re-open, the view is normal again.
The VBA editor window appears to be unaffected, although, at times, the
normal toolbars and menu disappears, but this is only an issue at design time
and I can live with it if I could fix my primary issue. The process that I
ran and left the db window in this state references Microsoft CDO For
Exchange 2000 Library, Microsoft ActiveX Data Objects 2.x, as well as DAO
recordsets and a few createobject (Excel.application).
All recordsets are being released, all instances of excel are being killed,
and the variables are set to nothing at the end of the process. I have
stepped thru the code a line at a time and all operate as expected, but leave
the UI in the aforementioned state. Am I going insane??