Support 1

[Support 1]

Unfortunately the mechanism used in Formativ to handle form/control events only supports standalone procedures. A VBScript class method cannot be an event handler.

For the moment the only way I can see to organize your procedures is by form name. That is, when an event handler procedure is created, the designer automatically gives it a name based on its owner form, eg. where the form name is “MyDialog”:

Sub MyDialogButton1Click(Sender)

Then all handlers belonging to a given form will appear together, in alphabetical order, in the Procedures group of the Code Explorer (treeview of globals, classes, procedures).

Note that it is possible to assign a handler to multiple events, even in different forms. This is useful when you want to perform the same action in different contexts. In this case I would try to keep things simple by giving the handler a general name. It may be appropriate for the handler to delegate to an object method (as with gMyClass.UpdateDateTime() in the above sample from Support 3), particularly if the object method is complex or depends on related methods/fields. In this way you can encapsulate much of the complexity inside a class. Obviously, a global reference to the object will be required, like the variable gMyClass.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this, which I will add to list of requested enhancements for a future version.

To fix the problem, rename the form in the Formativ IDE as follows:

• Click the Forms button (do not open the drop-down menu of existing forms). This will open the Forms dialog, which displays a list of the forms already in the applet.
• Select the item “Account Dialog” in the list.
• Click Rename… and enter a different name on the displayed dialog.
• Click Edit to edit the form, or Close to close the Forms dialog.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry. We may be able to help you extract the folder of interest into a new archive. For this we will need to review the archive metadata.

Could you send the following to support@advansyscorp.com please?

• The _metadata folder (zipped). The metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact.
• The full path to the relevant folder. You can copy the path from the original process log file, which logs the path to each folder that is processed.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

If you are using Archive To Go 1.5 (current release is 1.5.0.3) then you can select only the folders that interest you for archiving. This feature is only available for the main GroupWise account (ie. not for a GroupWise personal archive). Folder selection is available on the Folders screen of Archive To Go Creator.

The sub-folders within each selected folder will be included in the archive. All other folders will be excluded. The Viewer will show only the selected folders in the resulting archive.

Note that you can filter by date to further restrict the archived items.

I hope this helps.

Regards,
Advansys Support

[Support 1]

This enquiry has been replied to by direct email.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem. Unfortunately there is no fix available yet.

Would you consider trying out a special diagnostic version of the Viewer? This will assist our engineers in fixing the problem.

Out of interest, for approximately how long (days or weeks) had your machine been running when this error came up?

Regards,
Advansys Support

[Support 1]

This thread has been replied to by direct email.

Regards,
Advansys Support

[Support 1]

Thanks for reporting this problem.

A “Range check error” in the Viewer module of Archive To Go was fixed in the 1.5.0.2 release. This error occurred for messages which have HTML format available. It seemed to occur on machines which had been running for several days without being restarted.

I am not sure what you mean by:

>The archive could be opened and showed no errors
>on the same messages that generated the Range Check Error.

If this is the same “Range check error” that was fixed in 1.5.0.2, you would see many error windows pop up with this message – and the only way to stop it is to terminate the Viewer (using Task Manager). Is this the behavior you have seen?

Regards,
Advansys Support

[Support 1]

Thanks for the additional information.

We hope that you can provide the following information to help us better understand this problem:

• Which version of Archive To Go Creator was used to create this archive?
• Which version of Archive To Go Viewer are you using to view this archive?
• Please send the process log file to support@advansyscorp.com, preferably zipped. You will find it in the archive folder.

We look forward to your reply.

Kind regards,
Advansys Support

[Support 1]

Thanks for your enquiry. I believe the behavior that you describe has not been reported previously.

Just out of interest, what are the sizes of the original and A2G archives (approximately)?

What are your installed versions of the Creator and Viewer modules in Archive To Go?

When this archive was created, were any errors/warnings reported by Creator? You can find out by checking the summary at the end of the process log file, in the archive folder.

Please send the following to support@advansyscorp.com so that we can determine if the inaccessible messages can be salvaged:

• The process log file.
• The contents of the _metadata folder (zipped). The exported metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

When this archive was created, were any errors/warnings reported by Creator? You can find out by checking the summary at the end of the process log file, in the archive folder.

Has the archive been copied to a network, DVD/CD or other location?

Please send the following to support@advansyscorp.com:

• The process log file.
• The contents of the _metadata folder (zipped). The exported metadata contains only Sender, Recipients, Subject and Date for each message; it contains only Display Name and Email Address for each contact.

Regards,
Advansys Support

[Support 1]

Thanks for the clarification.

Our engineers have confirmed that Creator attempts to access the install folder in Read/Write mode. Limited accounts have Read-only access to this folder unless they are granted additional rights – as you have done.

This issue has been added to our list of enhancements for Archive To Go.

Many thanks for drawing this to our attention.

Regards,
Advansys Support

[Support 1]

Yes, Archive To Go Creator supports Caching/Remote mode.

You will need to enter the path to the caching/remote mailbox at Startup Arguments on the Account Selection screen, as in the following example:

/pc-C:NovellGroupWise<Caching/Remote Mailbox ID>

I hope this helps.

Regards,
Advansys Support

[Support 1]

Thanks for your enquiry.

We have not seen reports of a limited Windows account causing Archive To Go not to work. Can you provide more information about how “limited account users cannot open archive2go”, please? For example, what is the full text of the displayed error (if any)?

Which component of Archive To Go cannot be opened, ie. Creator, Indexer, Finder, Viewer?

If your limited account users are trying to run Finder/Indexer from a network location, perhaps this featured topic will help.

What is the version of Windows?

Regards,
Advansys Support

[Support 1]

Thanks for the clarification.

The error may have occurred because the text file size reached an unmanageable limit, or for some other reason.

Could you send the process log file (not the audit log file) in the target archive folder to support@advansyscorp.com, please?

What is the size of the audit log file?

I look forward to your reply.

Regards,
Advansys Support

[This message was edited by Support 1 on July 21, 2008 at 04:59 PM.]

[Author]

Replies