The trick with using VB is that you need to force the user to interact with the UT and take ownership away from VB. I do this in one of my programs by having an active link open a message box. This forces the user to interact with the UT and take ownership away from the program.
Make sense? Mark //SIGNED// MARK A. WORLEY, Contractor, 2 SOS/SYOS Remedy ARS Support, SAIC Commercial: (402) 294-8226 DSN: 271-8226 mailto:[EMAIL PROTECTED] -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Wednesday, October 03, 2007 15:58 To: arslist@ARSLIST.ORG Subject: Re: Opening the User tool via VB? The issue with this... Aruser /user="Demo" /password="remedy" Or Aruser -user="Demo" -password="remedy" ...is that he wants to open a specific form. This will open the UT, but not the form he wants. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Davies, J.T. Sent: Wednesday, October 03, 2007 3:49 PM To: arslist@ARSLIST.ORG Subject: Re: Opening the User tool via VB? ** Hi Matt, I could see why the first scenario did that. It's the VB app that has a handle on the called app, so when your app closes, so do all processes spawned from it. In the second...somethings missing and I can't place my finger on it, but, to answer your question, according to the KB: For example, the syntax to start BMC Remedy User with a login name and password is: Aruser /user="Demo" /password="remedy" Or Aruser -user="Demo" -password="remedy" That might/should work. J.T. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Perrault Sent: Wednesday, October 03, 2007 1:22 PM To: arslist@ARSLIST.ORG Subject: Opening the User tool via VB? ** All, I'm trying to create a VB script to Open the User tool, Login, and Open a form. I was able to pull some of the examples. But they don't work. Here's what I tried: Dim App Dim ARForm Dim sessionId Dim Description Set App = CreateObject("Remedy.User") sessionId = App.Login("Login Name","Password",False) Set ARForm = App.LoadForm(sessionId,"Server_Name", "Form Name","entry_Id",4,True) Well, all that does is, open the Tool, Login, open the form, and then the user tool exits/closes. I want the User tool to stay open and not close. So I tried this: dim objShell Dim App Dim ARForm Dim sessionId set objShell = CreateObject("Shell.Application") objShell.ShellExecute "aruser.exe", "", "C:\Program Files\AR System\User\", "open", 1 set objShell = nothing Set App = GetObject(, "Remedy.User") sessionId = App.Login("Login Name","Password",False) Set ARForm = App.LoadForm(sessionId,"Server_Name", "Form Name","entry_Id",4,True) Well, that launches the User Tool, but doesn't login. So I'm wondering if there's a way to pass the login credentials via the command line? If anyone has any other suggestions on how to do this I would appreciate it. Thanks, Matt __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"