"Coult not find specified object" and "Path-File access error" messages

[Robert Crandal]

I am starting to see "Run Time Error 75 - Could not find
specified object" and I believe it is related to the modeless Userform
that I am using. Here are my modeless userform definitions:
-------------------------------------------------------------------------------
Private Declare Function FindWindow Lib "user32" Alias "FindWindowA" ( _
ByVal lpClassName As String, ByVal lpWindowName As String) As Long
Private Declare Function SetWindowLongA Lib "user32" _
(ByVal hWnd As Long, _
ByVal nIndex As Long, _
ByVal dwNewLong As Long) As Long

Private Const GWL_HWNDPARENT As Long = -8
------------------------------------------------------------------------------
Private Sub UserForm_Initialize()

Dim hWnd As Long

hWnd = FindWindow("ThunderDFrame", Me.Caption)
SetWindowLongA hWnd, GWL_HWNDPARENT, 0&

End Sub
-------------------------------------------------------------------------------

The above code allows me to create a nice modeless popup. I have not
experienced any problems with this popup until tonight. I displayed the
popup a couple times for test purposes, then I left my computer for about
5 minutes. When I came back, I tried to display the popup form again and
that is when the above error displayed on my screen.

Why would the form display properly, then 5 minutes later it displays an
error??
All I did was press a button on my spreadsheet that loads the form using
"Userform1.Show vbModeless", and then it crashed....

Even more odd, when I tried to view my form object in my VBA project window,
it gave me the following message: "Path/File access error".

Has anybody ever experienced this behavior and resolved it???

thank you

 

[joel]

A window can have more than one pane such as with an IE explorer window
can have more than one tab. The window name will change as you activat
each tab. Application can also have activeX controls that will chang
the active window such ad AdWare. I don't know what is cuasing th
problem but I would see if the window Name that you are trying to acces
changes and that is the cause of the problem.

You may want to check all processes instead of windows. The windo
would be the parent of the process.

I wouold be nice if Microsoft allowed the Task manager to view th
Process ID and the Parent Process ID. You can view the Process ID bu
not the parenet so you can track these type problems. Unix/Lini
operating system does show both. In window you can get the parents an
chid process but you have to write your own code. I think I've see
utilites that will do this but it has been a number of years since I ha
to write code that required this

 

[Rick Rothstein]

Are you using the API code simply to show your UserForm as modeless (in
other words, so you can use the worksheet while the UserForm is displayed)?
If so, you don't need to use the API function calls at all... just use this
statement to show your UserForm...

UserForm1.Show vbModeless

Obviously, change the name of the UserForm from my example UserForm1 to
whatever the name of your UserForm actually is.

 

[Robert Crandal]

The API functions, specifically "SetWindowLong", are used to set some
special properties for the userform window. It creates a type of popup
userform that stays kind of detached from Excel and remains visible even
when
Excel is minimized. I was really hoping to use this style of popup, but
it's
causing those weird errors. 8(

Robert