Support 1

[Support 1]

There is no generic Hint/ToolTip control available. However most, if not all, visual controls have a Hint property (text). There is also a matching ShowHint property (true/false) which could be used to support different configurations.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Just to confirm, does the error appear if you run Templates on another machine while logged in to the same account as on the affected machine?

Please send the Formativ configuration from the affected machine to support@advansyscorp.com. You can obtain the configuration by selecting Help | About Formativ… from the GroupWise main menu. When the About Formativ dialog appears, go to the Configuration tab and click the button Copy to clipboard. Then paste the text into your reply email (or save it to a plain-text file and include it as an attachment).

Regards,
Advansys Support

[Support 1]

>if the user put the start and end date manually in the fields nothing happens…

I am not sure what you mean by “fields”. Are you referring to the DateTimePicker or Edit control? I suggest that you permit users to choose dates using only the DateTimePicker.

You can compare the Date properties of two DateTimePicker controls as shown in the example below:

'Datefunction Start
Sub PickerStartChange(Sender)
  dim fromDate
  dim toDate

  fromDate = TasoUrlaub.PickerStart.Date
  toDate = TasoUrlaub.PickerEnd.Date
  if toDate > fromDate then
    MsgBox "Start date cannot be later than End date."
  end if
End Sub

Your OnChange handler can also be used to fix an incorrect date after a user has broken the rule, as shown below:

'Datefunction Start
Sub PickerStartChange(Sender)
  dim fromDate
  dim toDate

  fromDate = TasoUrlaub.PickerStart.Date
  toDate = TasoUrlaub.PickerEnd.Date
  if toDate > fromDate then
    MsgBox "Start date cannot be later than End date."
    TasoUrlaub.PickerStart.Date = TasoUrlaub.PickerEnd.Date
  end if
End Sub

Another option is to use the OnUserInput event if you want to prevent a change to the date that breaks the rule. Note that you will need to edit the handler that is created automatically – add the ByRef keyword as shown below:

Sub PickerStartUserInput(Sender, UserString, DateAndTime, ByRef AllowChange)

  dim fromDate
  dim toDate

  fromDate = TasoUrlaub.PickerStart.Date
  toDate = TasoUrlaub.PickerEnd.Date
  if toDate > fromDate then
    AllowChange = false
  end if

End Sub

In addition, I suggest using the built-in VBScript named constants, eg. vbSaturday, vbSunday instead of “magic numbers” like 7, 1, etc.

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 1 on October 06, 2008 at 08:28 PM.]

[Support 1]

Thanks for the additional information.

If the errors listed in your logs are all similar to:

quote:

---

Cannot access folder “RFP-Dupont”

---

then there may be some corruption in the mailbox database.

I suggest you download and install the latest release (1.5.0.3) which includes some memory management optimizations that may prevent these errors. But before attempting to re-archive any of the problem mailboxes, please try the test described below.

If the GWCheck report says nothing is wrong with any of the problem folders, then I suggest you try the following using 1.5.0.3.

• Set a filter that will exclude all messages, in order to test folder archiving in the minimum possible time. A filter for this might be the date range: tomorrow or later.
• If the previous step does not reproduce the errors, try re-archiving without setting a filter.
• If the folder archiving test reproduces the errors, try moving the items from each affected folder to a new folder, eg. from “RFP-Dupont” -> “RFP-Dupont1”. Then delete the old folder and rename the new one as the original name. Then try re-archiving.

If you continue to get these errors, please send the process log (zipped if larger than 200 KB) to support@advansyscorp.com.

Finally, we do not have statistics available for how long it takes Archive To Go to archive 1 GB (for example). It would not be trivial to calculate such a statistic because so many variables are present in a GroupWise environment, eg. network latency, disk fragmentation, total mailbox database size. However it is likely that 1.5.0.3 reduces the time significantly due to the optimization mentioned above.

I hope this helps.

Regards,
Advansys Support

[This message was edited by Support 1 on October 06, 2008 at 06:00 PM.]

[Support 1]

Thanks for your enquiry.

To create a handler for DateTimePicker’s OnChange event, double-click the edit box at OnChange in the Object Inspector. For a DateTimePicker named Picker1, this creates a Sub like that shown below:

Sub Picker1Change(Sender)

End Sub

There is no Value property for DateTimePicker (the Object Inspector displays the properties Date and Time).

If MainForm has a Label named Label1 for displaying the date as it changes, you could modify the handler as below:

Sub Picker1Change(Sender)

  MainForm.Label1.Caption = DateToStr(MainForm.Picker1.Date)

End Sub

You can also use the VBScript functions listed below to help with formatting date/time values:

Hour
Minute
Second
Weekday
Day
Month
Year

You may find it helpful to compare DateTimePicker with the RzDateTimeEdit control (on the Enhanced tab). This control has the event OnDateTimeChanged along with a range of different properties.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

It might be helpful to obtain a diagnostic trace of SmartField Assistant’s progress. In order to gather diagnostic information about it, you will require a debug event viewer. If you do not already have one, I suggest you download and install DebugView from http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx, and follow the steps set out below:

• Start DebugView and turn off capturing for Kernel events (if available).
• Go to GroupWise and press Ctrl+Alt+D (3 keys) as you start SmartFields Assistant; this will make it generate debug information.
• Save the debug information captured in DebugView to a text file, and send it to support@advansyscorp.com.

In addition, which edition/version of Windows are you running?

I look forward to your reply.

Regards,
Advansys Support

[Support 1]

Further to the previous post, we plan to include a function in version 2.0 for extracting selected messages from an existing Archive To Go archive. The messages could be selected by searching for certain keywords, or by selecting one or more folders.

At this stage we expect version 2.0 to become available around March 2009.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

I think it is possible to develop a custom tool to extract an arbitrary folder (or folders) from an Archive To Go archive. If you would like us to do such a custom development, please write to sales@advansyscorp.com with a detailed description of your business and technical requirements. This will enable us to provide you with a quote for the development, and proceed from there.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

The behavior you describe has not been reported previously. However, there is a known issue with message properties being unavailable for shared incoming folders, given the conditions listed below:

• The affected mailbox is a native/personal GroupWise archive which is included for archiving with the main mailbox and GroupWise is switched to the main mailbox, or
• The affected mailbox is the main mailbox which is included for archiving with a native/personal GroupWise archive and GroupWise is switched to the native/personal archive.
• The version of GroupWise is 7.0.2 HP or below (I believe the problem was fixed in 7.0.3).

The workaround for this is to archive each mailbox by itself, if message properties are required.

If this does not describe the problem you have found, please send to support@advansyscorp.com the process log file, which you will find in the archive folder (zipped if larger than 200 KB).

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

We do intend to add encryption in the next major release, along with batch processing and incremental archiving. Unfortunately I cannot give you an expected release date (at present we are fully occupied with compatibility testing for the imminent release of GroupWise 8). It’s possible that these features will be included in successive releases of Archive To Go; at this stage batch processing is likely to be the first available.

Regards,
Advansys Support

[Support 1]

According to the GroupWise online help, the command-line switch for a remote-mode login is “/pr” (the error text indicates “/pc” was used).

If changing the command line to “/pr-Y:763049hittheroad” does not work, you may need to confirm that the remote mailbox path is correct.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Sam wrote:

>Looks like the switch wasn’t being flicked properly

Formativ 2.0.0.12 is unaware of the issue with XP themes and consequently does not attempt to switch off themes when displaying the Forms editor. The fix is only available in Formativ 2.0.1.

Short of upgrading to 2.0.1, the workaround (as you have found) is to turn off XP themes in the Windows display properties. Unfortunately this will be necessary for every user of Studio/Creator in your organization.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

Please copy the log header section into an email and send it to support@advansyscorp.com. The header section contains details of your Windows environment and the Archive To Go settings (up to the separator line).

Do these errors occur when:

• Using a different machine to archive the same mailbox?
• Processing the user’s main mailbox, or a native/personal GroupWise archive, or both?
• Processing a shared incoming folder?

Regards,
Advansys Support

[Support 1]

To the best of our knowledge, Formativ does not make it possible to override a control’s WindowProc method. This appears to be an essential part of implementing drag and drop to operate beyond the bounds of a form.

Regards,
Advansys Support

[Support 1]

You are welcome.

In some circumstances it may be preferable to develop part of a GroupWise solution as a COM/ActiveX object. The object can then be used by Formativ/VBScript in whatever GroupWise contexts the solution is required.

I expect you are aware that developing a COM/ActiveX object requires a COM-compatible language, eg. C++, Delphi, VB or any of the languages that support Microsoft .NET. This post describes the issues to be aware of when developing a COM/ActiveX object using .NET.

Regards,
Advansys Support

[Author]

Replies