Repost from General Questions- Bizarre Behavior

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

Guest

Good day all...
Jerry Whittle said:
Insane? Join the club!

Actually I think that you have a hardware or OS problem. Possibly there
isn't enough video memory or processing power for the graphics. Try
right-clicking the desktop and bringing up properties. Then go to the
Settings tab. Select a lesser screen resolution and/or less colors. See if
that helps.

Sometimes something as simple as an updated driver for your graphics card
can fix such problems.
Click to expand...



Brought my resolution down to 800X600 16 colors..

still the same.

My computer is locked down so I can't update the drivers, although they were
last updated 6/21/2007 (driver date)

Of course, it didnt work..that'd be too easy. Arrgghhhh

I run numerous access applications throughout the day, with this particular
one the only problem. D
 
In addition, there is a form open, but I
can not view it.
Click to expand...

Is it an invisible pop-up/modal form (if such a thing is possible)?

That is, is the form demanding attention you can't give it?

Geoff
 
No. The properties for the form are visible and not modal.
Thanks for the idea though. At least some one is reading these posts. :P
 
Drayton T. said:
No. The properties for the form are visible and not modal.
Thanks for the idea though. At least some one is reading these posts. :P
Click to expand...
<SNIP>

This is pure guesswork. Do you happen to be using a timer on one or more of
your forms? I ask because these can cause bizarre behaviour if not properly
handled.
 
Continuing from above, just a few further thoughts:

1:
Have you gone to the Microsoft website and downloaded all security and
critical upgrades for your version of Windows and Office. (Windows and
Office updates are on different pages @ Microsoft)


2:
references Microsoft CDO For
Exchange 2000 Library
Click to expand...

Might be worth posting your issue to the following newsgroup:

microsoft.public.outlook.program_vba

The MVPs there would know any issues relating to CDO for Exchange.


3:
references ... Microsoft ActiveX Data Objects 2.x, as well as
DAO recordsets
Click to expand...

I doubt this is an issue - if it were your code probably wouldn't run - so I
hesitate to mention it - but specifying the class in a variable declaration
can be important when using ADO and DAO recordsets. So you'd probably want
to declare as follows to be on the safe side:

Private objADORS As ADODB.Recordset
Private objDAORS As DAO.Recordset


4.
Again, I don't suppose it'd help, but, if you haven't already, it might be
worth explicitly closing the recordsets, if they exist, before
disassociating the variables, as in:

If Not objDAORS Is Nothing Then
objDAORS.Close
End If
Set objDAORS = Nothing


Good luck! I hope you solve it before cracking up! (Know the feeling!)

Geoff

 
Back
Top