FollowHyperlink opens a file, but not visible

[RoyPayne]

Access 2010
Full Office 2010 software
Win 7 64 bit

Using the FollowHyperlink method and passing a known/good file path & name, the file opens succsessfully, but in the background, with the database still visible. The user has go to the task bar and manually click the file icon to make it visible. I cannot figure out how to force the file to open visible & on top. The form properties are Popup = True, Modal = False

Here is my code (this code worked fine in previous versions of Access)

Sub OpenDocument(DocPathName)
 
On Error GoTo errorHandler
 
    'If the document path and name have not been filled in, display this message:
    If IsNull(DocPathName) Then
        MsgBox "You must first enter the document path and file name. Use the Select button to locate and select the file."
      Else
 
        'Now use the path & file name entry and attempt to open the document.
        Application.FollowHyperlink DocPathName
 
    End If
    Exit Sub
 
errorHandler:
    'If the document was not opened using the path as entereed, display this message to the user:
    MsgBox "The document " & DocPathName & " cannot be found. " _
         & "Please check all of the charactures in the path and file name to make sure they are correct."
 
End Sub

[zmbd]

Try changing your current line 11:
Application.FollowHyperlink DocPathName

to:

Application.FollowHyperlink _
   Address := DocPathName, _
   NewWindow : = true

See if forcing a new window will cause it to open full and on-top.

[RoyPayne]

Thanks for the reply but that does not work. I actually already tried setting the NewWindow property to True. The file still opens, then immediately goes down to the task bar with the database still visible

[zmbd]

I think you're going to have to get the application as an object... for example:

>>The following is air code!
if: DocPathName = "C:\ExcelReport.xls"
then:

Sub OpenDocument(DocPathName) 
 
   On Error GoTo errorHandler 
   Dim xlObj As New Excel.Application
   If IsNull(DocPathName) Then
      MgBox "You must first enter the document" & _
          "path and file name. " & _
          "Use the Select button to locate and" & _
          " select the file." 
      Else 
         Application.FollowHyperlink DocPathName
         Set xlObj = GetObject(, "Excel.Application")
         xlObj.ActiveWindow.WindowState = xlMaximized
   End If 
Exit Sub 
errorHandler: 
   MsgBox "The document " & DocPathName & _
          " cannot be found. " & _
          "Please check all of the charactures" & _
          " in the path and file name to make" & _
          " sure they are correct." 
End Sub 

So, for Line 4 and 12 you'll need for the correct application.
You might find the last example interesting:
Using the CreateObject and GetObject Functions

[RoyPayne]

Let me try that, I'll let you know if it works

[RoyPayne]

Bingo, that fixed it! In my case I used Word.Application, but it now opens with the document on top. If anybody is having that problem, use lines 12 & 13 above, it works!

Thanks zmbd, you da boss

[NeoPa]

That will work because (I believe) maximising an application window sets its .Visible property to True automatically.

As standard, when you use CreateObject() (or even when you use GetObject() to open a new window as opposed to a pre-existing one), the .Visible property is False.

To get it to show without making any other changes simply say :

xlObj.Visible = True.

See Application Automation.

[RoyPayne]

Actually the above fix from zmbd did NOT fix the problem. It looked initially like it did because the Word doc I was trying to open was finally staying on top/visible with the additionas of lines 12 & 13 above. However it turns out that the reason the doc was staying visible is because line 13 was triggering an error - "Runtime error 5853 - Invalid parameter". I tried several things to resolve the error, could not get it resolved. So I just put in an "On Error Resume Next", that got rid of the error message but now the Word doc goes right back to the background/not visible, have to click the icon in the task bar to see it. The only way it stays visible is letting it trigger the above error.

Anybody else have an idea how to resolve this?

[zmbd]

As always
We need to have you perform the general troubls shooting first as outlined here:
> Before Posting (VBA or SQL) Code
Once that is done (if possible (^_^)) then follow the instructions there in to post your actual code.

When posting errors:
for each error (if any): the EXACT title, error number, and descriptions that occurred, please do not abreviate nor alter the text,,
and at what line in your posted code the error occurred.

[RoyPayne]

Ok, what the HECK are you talking about? I did not abbreviate anything. And I posted the EXACT title and error number. And I told you the exact line of code it happened on. If you don't want to respond any further with suggestions on how to fix this that's fine, but I am not interested in all of your "rules".

If anybody else has any suggestions on how to resolve this I would appreciate the help.

[zmbd]

Ok, what the HECK are you talking about? I did not abbreviate anything. And I posted the EXACT title and error number.

RoyPayne:
There is a nicer way to state that... something like:
""Z, that was the whole error message""
""Z, as far as I know that was the error message""
etc...

The reason I asked for the full text:
Runtime 5853 is not a standard MS Access error
Microsoft Access 2010 Error Numbers and Descriptions Thus, the inquiry to post the exact text.

Oh, and BTW: You might want to read thru all of those errors, there's only about 1300 or so, many of them repeat the text from one to the other with only a word or two variation and yet others, will have %1, %2, %4 and other wildcard replacements available to Office/Access so the numeric can stay the same and the text differ. Sometimes these errors will also appear with a title in the prompt and yet other times the same message will show up in just a message box with an [OK] button and no title nor even a number. All of that information is valuable in trying to determine if ACC, OFF, OS, or what tripped the error.

If you like you can actually build your own local table of Access errors by following the instructions here:
MS KB105666: ACC: How to Find Access Basic Error Codes
Let me know if 5853 shows up in your table... it's not in mine and I have the latest and greatest of the ACC2010 setups. (^_^)

And I told you the exact line of code it happened on.

RoyPayne Post#6 Bingo, that fixed it! In my case I used Word.Application,

And yet you did not post your modified code
Are you still using:
Line13:xlObj.ActiveWindow.WindowState = xlMaximized from the original code I posted. Or did you use the code from the example I pointed out in the link provided in Post#4 along with that posted code?
How am I to know?
Once again, there was a nicer way to provide the information.

(OH, and that line of code may not be the root cause, it could be that we didn't get the correct object in the lines before; however, without your modified code... who's to know?)

If you don't want to respond any further with suggestions on how to fix this that's fine,

That comes across a bit snarky, doesn't it!
I am trying to help you.
The questions asked are in an attempt to understand what is happening.
If you don't want to help us to help you, then that's fine... I have others on the site that I'm trying to help too...

but I am not interested in all of your "rules".

How is it unreasonable to ask you to follow the troubleshooting section of the link given? I can't perform those steps on my PC for you, for one, we don't have the same setup and I don't have your file.
As for the rules contained therein the link provided, I didn't write them, the Senior staff and Site Administrators did; thus, they apply to everyone... including myself, even as a moderator, and you should have read them before making your first post. The rules in that link were not my primary focus though for providing the link, the basic option setup and troubleshooting steps were: (

zmbd:Post9: We need to have you perform the general trouble shooting first as outlined here:

If anybody else has any suggestions on how to resolve this I would appreciate the help.

And NeoPa has already stepped in once as I am sure others will do the same if something jogs their memories about a similar situation. Normally we’re fairly helpful group of people.

RoyPayne: Please keep in mind that moderators, experts, and others are un-paid volunteers that attempt to provide some help and guidance in-between our obligations to work and family – we do not work for you , you do not get to use bad language nor stomp your preverbal feet at us.

[RoyPayne]

Ok. I posted the error message exactly as it appeared.

I will seek help elsewhere. Thanks anyway.

[NeoPa]

Just to be absolutely clear for any others that might read this thread and infer that such obnoxious behaviour is tolerated on this site, Roy was given some extra leeway because the person dealing with him is a helper of vast experience and unlikely to be put off by such behaviour (He's a father of young children so used to such).

We do expect site rules to be adhered to, with respect to general manners as well as all the other requirements you sign up for with your membership. It is critically important that any members who spend their time trying to help others can know that they will be protected from any such behaviour, and believe me, they will.

All members can help with this by reporting any such misbehaviour when they see it. We generally find that these are noticed and dealt with before anyone gets a chance to report them, but I assume it's possible for some to be missed sometime, so please report any you see and we'll deal with them appropriately.