Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Author
    Replies
  • in reply to: Error on startup: TScript.Loadfromstream #5321
    mickeyd
    Participant

      Hi,

      I’m unfortunately unable to send any configuration information as our corporate network is not connected in any way to the Internet.

      We had found the offending applets causing the error, but I can’t see how it would be a problem with the applet since they work just fine for the rest of our 2999 employees. Just thought something on his account must not have been set up properly.

      Was just browsing for ideas and was hoping you’d already solved this for this other guy. We’ll figure it out. Thanks.

      in reply to: Error on startup: TScript.Loadfromstream #5319
      mickeyd
      Participant

        Hi,

        Just wondering if this was ever resolved as we have the same problem for one (and only one) of our users.

        in reply to: Identifying Outgoing Messages #8265
        mickeyd
        Participant

          That works perfectly! Thank you!!

          in reply to: Groupwise Accounts with Parentheses causing Error on BusySearch #8242
          mickeyd
          Participant

            Well, I found the offending line of code! The bug is not in the call to BusySearchDlg, but in the call to another Token: ItemSetText.

            When appending resource names (room number) to the appointment recipient list, we used:
            Groupwise.ItemSetText(“X00”, itfTo, strRoomNumber, TRUE)
            and that is the command that doesn’t like parentheses in the account display names.

            And I found a workaround! I now use TextSetTo instead of ItemSetText to append the room number and it works just fine for all account display names, with or without parentheses:
            Groupwise.TextSetTo(strRoomNumber, TRUE)

            Just thought I’d share the solution. Thanks.

            in reply to: Looping Through All Appointment Recipients #8233
            mickeyd
            Participant

              Thank you, I finally did get that to work using the Object API.

              It was a bit of a challenge in a bilingual work environment as the folder path to send to the Groupwise.ItemSaveMessageDraft function must be in the user’s language, however the Groupwise.Account.WorkFolder.Name function only returns the English value.

              So it seems I may have to resort to hard-coding the strings for our French users, which may cause some errors down the road.

              After much trial and error, I found that in the version of Groupwise that we have (GW7), the workfolder path needs to be:

              (English)
              folderPath = Groupwise.Account.Owner.DisplayName & ” – HomeWork in Progress”

              (French)
              folderPath = Groupwise.Account.Owner.DisplayName & ” – AccueilTravail en cours”

              This doesn’t seem to be documented anywhere, so maybe this will save someone else a headache or two…

              Thanks for your help.

            Viewing 5 replies - 1 through 5 (of 5 total)