Forum Replies Created
-
AuthorReplies
-
Thank you very much for giving it a try. I’ve been getting error messages, but I don’t know the system well enough to be able to tell if it was a syntax error on my part, or a “doesn’t work, as designed” limitation of the API.
I really appreciate you guys working out the solution (even if the answer is “it’s broken”)
Thank you very much.
That helped.
It is broken on two versions: GW 7.0.1 (build 364 – June 13, 2006); GW 7.0.1 IR 1 (build 553 December 14, 2006)
But it ran without error on GW 6.5.1 (July 11, 2003).
February 15, 2007 at 3:38 pm in reply to: Want to use Formativ to update my signature – anything special required? #7816Thank you very much.
Do you know if the inability to replace an existing signature is “working as designed” ?
February 13, 2007 at 4:29 pm in reply to: Want to use Formativ to update my signature – anything special required? #7817One other question:
the string I’m sending it is getting stripped of linefeed / carriage return characters. What is the correct way to send those through?
Thanks!
February 13, 2007 at 4:28 pm in reply to: Want to use Formativ to update my signature – anything special required? #7818Thank you for the info – it helped me figure out why my original program wasn’t working.
As it turns out, both programs work if I delete my existing signature first. If I do not, then no update happens.
The token throwing version is nice in that the msgbox tells me the return value is true; the code did what it was supposed to. The error must be further down the line, what with running into an existing signature, and not just wholesale replacing it.
January 3, 2007 at 8:00 am in reply to: New appointment registered as “free” – did I miss something? #7792Thank you – that explains it.
Thank you very much for both pieces of advice.
“CloseGW.exe” is just a WinBatch I wrote myself. I’m not fond of that idea because it means I either have to run a shared .exe off a file server, -or- copy the freakin’ .exe to 1700 workstations. Yuck.
The example from the Windows Script Host worked great on my particular machine. I’ll try deploying it to the 60 people here in IT to see if it causes anyone any particular grief before deploying it wider.
Yes, you’ve been very helpful. Thank you.
Trying another way to shut down the GroupWise client, should a user decline the Acceptable Use Policy.
I have written a program which closes the GroupWise client – all I need now is a method to launch it when the user declines the AUP.
GroupWise.RunProgram(“CloseGW.exe”,””)
I hate this, because it is kludgy. But if I can get it to work, it will be better than admitting I just can’t get the job done.
Would have thought this would do it, except I get “Cannot use parentheses when calling a Sub at line… (specifies end of statement)”
How do I get this method to go?
Thank you.
By dinking around, I found that the proper syntax for AppAllowClose is just a one or a zero.
Problem is, the code still does not work.
GroupWise.AppAllowClose(0)
GroupWise.AppClose()or
GroupWise.AppAllowClose(1)
GroupWise.AppClose()produces no discernable action (except that GroupWise.AppAllowClose(0) turns off the Exit option under the File menu.
In theory, I found it. In practice, I’m still missing something.
‘ Exit GroupWise if the policy not accepted by the user
if not IsPolicyAccepted() then
Groupwise.AppAllowClose(Yes!)
GroupWise.AppClose()
end ifI get an error on the Groupwise.AppAllowClose(Yes!) line.
-
AuthorReplies