MIE Software Support Note
Subject: |
Summary of known Summit Pro 2000 issues |
| Applies To: | Summit Pro 2000 |
| Date: | 7 October 1999 |
Installing Summit Pro 2000
CD does not install Summit Pro 2000
System "hangs" while installing Summit Pro
2000
Installation halts with message that wininet.dll
and/or urlmon.dll cannot be written to
Installation halts with message that msexcl35.dll
could not register itself
Launching (starting) Summit Pro 2000
Summit Pro 2000 does not open. Gives message that you
don't have permission to convert the database
Summit Pro 2000 takes a long time to open
Running Summit Pro 2000
Browse button does not work or error opening file name
dialog box
Internet Assistant displays as a blank grey form
Pictures and lines lost on e-mailed correspondence
Slider bars missing or not working
in the Name Badge and Ticket Design or Letterhead Designer forms
"Some data may not be displayed" message when
previewing labels/badges - may be followed by application failure
"Invalid page fault in module vba332.dll" message
after upgrading Summit Pro 2000 and application will not start
CD does not install Summit Pro 2000
When you install the MIE Software CD the setup program that runs automatically does not install the Summit Pro 2000 application. If the CD you received is marked MIE Sampler CD a help file detailing the contents of the CD is installed. If the CD you received is marked MIE Software Collection the MIE Software Installer is installed.
To install Summit Pro 2000 take the following steps.
1. Click Start then Run
2. Click Browse and locate the sp2000r.exe file on the CD
3. When sp2000r.exe is displayed in the Open text box click OK to start the Summit Pro 2000 installation program.
System hangs while installing Summit Pro 2000.
The setup program for Summit Pro 2000 stops while trying to unzip the sp2000.mdb file. If this occurs it is because you have Vet Anti-Virus Protection resident file monitoring enabled and you are running an old version of Vet which has a fault when examining large Microsoft Access 97 databases. The fault causes Vet to either:
i. Report the presence of a Suck.A macro virus in sp2000.mdb and halt the installation process
or
ii. Take a very long time (45 minutes plus) to examine the sp2000.mdb file during the installation process. The time taken is so long that on some computers the system appears to hang.
This problem relates to Vet examining large mdb files and has been corrected in Vet version 10.0.1.11 which is now available for downloading from their website http://www.vet.com.au/html/download.html. We have tested Vet version 10.0.1.11 and can confirm that the problem has been fixed.
When you download from the Vet website, ensure that you download the full version, not just the update.
If you are not certain what version of Vet you are running, select About... from the Vet Help menu. This will display the following dialog box with the version information:
Installation halts with message that wininet.dll and/or urlmon.dll cannot be written to
This problem can occur if you have later versions of these files on your system or these files are open by another Windows application. In either case you will be shown Abort, Retry and Ignore buttons. Click Ignore and the installation will continue normally.
Installation halts with message
that msexcl35.dll could not register itself
or
Summit Pro 2000 does not open. Gives message that you don't have permission to
convert the database
Summit Pro 2000 is written in Microsoft Access 97 and installing Microsoft Office 2000 Professional or Premium(which include Microsoft Access 2000) can remove components and references needed to run Microsoft Access 97 programs. Click here for more information.
Summit Pro 2000 takes a long time to open
Rewriting Summit Pro 2000 in Microsoft Access 97 has resulted in a much larger Summit file that takes a lot longer to load than earlier versions of Summit. To give comparable peformance with earlier versions we specify the minimum processor as Pentium 200 and minimum RAM requirements as 64MB (Summit Professional was 32MB minimum) and have a recommended RAM of 128MB or more.
|
Indicative times for launching a
recently compacted copy of Summit Pro 2000 are: Pentium 166 with 32MB RAM 6minutes |
|
Another factor in start up time is database size. We find that Microsoft Access 97 databases grow in size much more quickly than the old Microsoft Access version 2 databases did. This also slows down start up time dramatically. We recommend that you compact Summit Pro 2000 at least twice a week.
Browse button does not work or error opening file name dialog box
If you receive a message similar to "Run-time error '424': Object required." it means that the application has not been able to open the Windows File dialog box due to a problem in the Windows registry. This problem usually occurs when you are trying to open event files and have clicked on the Browse button.
To work around this you need ensure that the common dialog control (comdlg32.ocx) is correctly registered. To do this take the following steps.
1. Click Start and select Run
2. Enter "regsvr32.exe comdlg32.ocx" (without the quotes)
If this does not correct the problem take the following steps.
1. Remove Summit Pro 2000 using the Control Panel utility Add/Remove Programs
2. Reinstall Summit Pro 2000
3. Click Start and select Run
4. Enter "regsvr32.exe comdlg32.ocx" (without the quotes)
Internet Assistant displays as a blank grey form
On some installations, the Internet Assistant form can display as a blank form with none of the fields on the form shown. This is caused by a missing record in the InternetRegistrationSettings table.
To rectofy this problem take the following steps.
1. Open the After Menu
2. Click on Database Table Access
3. Enter the name of the table as InternetRegistrationSettings and click OK. This will display a table similar to the one below.
4. Click in the DUChecked check box and then clear the DUChecked check box to force the required record to be created as shown below.
5. Close the table.
Pictures and lines lost on e-mailed correspondence
When you e-mail correspondence from Summit Pro 2000 the correspondence the correspondence is converted to either text, HTML or RTF and the converted file is then attached to the e-mail message.
While the output formats of RTF (Rich Text Format) and HTML (Hypertext Markup Language) support embedded or linked graphics, Microsoft Access 97 does not support outputting an OLE object to another file format and as a result the pictures and lines on the correspondence are lost.
Refer to Microsoft article http://support.microsoft.com/support/kb/articles/Q169/2/77.asp for more information.
This problem only applies to e-mailed correspondence, it does not apply to printed or faxed correspondence.
Slider bars missing or not working in the Name Badge and Ticket Design or Letterhead Designer forms
If you receive the above message when opening the Name Badge and Ticket Design or Letterhead Designer forms it is because there is a problem in Windows with the slider controls used to design letterhead, badges and tickets. There are two reasons for this problem, one is licensing (refer Microsoft article Q172859) the other relates to a known problem in Microsoft Access 97 (refer Microsoft article Q177908).
To fix this problem take the following steps:
1. Remove the Summit Pro 2000 software using the Add/Remove Software utility on the Control Panel.
2. Delete the SP2000 folder and all sub-folders.
3. Download the comctl32.exe program.
4. Locate the comctl32.exe program using Windows Explorer and then run it by double-clicking on it.
5. Press the Start button, select Run, enter regsvr32.exe comctl32.ocx and press OK.
6. Download the sp2000s.exe upgrade file.
7. Install and open Summit Pro 2000.
8. Double-click on the sp2000s.exe file in Windows Explorer or File Manager. This will unzip the sp2000.udb file to the c:\sp2000 directory.
9. From the Summit Pro 2000 main menu click on the Upgrade button. Click Browse and you should see the sp2000.udb upgrade database.
10. After locating sp2000.udb, click the Complete the upgrade button.
"Some data may not be displayed" message when previewing labels/badges - may be followed by application failure
The message "Some data may not be displayed. There is not enough horizontal space on the page for the number of columns and spacing you specified." may be displayed if you are producing address labels or name badges using stationery with no margin or a very small margin. This is because Microsoft Access 97 does not recognise a zero margin any longer and looks at your printer's unprintable area to determine if the labels/badges can fit on the page. As the unprintable area varies from printer to printer this message may appear with some printers, but not with others. When you press OK, Access may also crash if you have positioned any name badge or ticket elements within your printer's unprintable area. There are three ways of dealing with this problem.
1. Change stationery.
Change to a name badge or address label stationery with wider margins around the border of each page. If the width of the margin is greater than your printer's unprintable area the message will no longer be displayed.
2. Reduce the setting of your printer's unprintable areas.
Some printers, such as the HP Laserjet IIP Plus, allow you to override the default settings for the unprintable area. In the HP Laserjet IIP Plus example, click Start, then Settings, then Printers and right-mouse click on the HP Laserjet IIP Plus and then select properties as shown below.
From properties, select the Paper tab, and then click on Unprintable Area and reduce the unprintable settings as shown below.
Note that not all printers allow you to modify the unprintable area settings.
3. Ignore the message and click OK. In the case of address labels all information will be displayed although . In the case of name badges or tickets you may get an application crash.
"Invalid page fault in module vba332.dll" message after upgrading Summit Pro 2000 and application will not start
This problem may occur if you have just upgraded Summit Pro 2000 or you have been modifying the software and have performed Copy and/or Save As operations on objects which contain code and have then closed down the software package without recompiling.
If you have Microsoft Access 97 on your computer take the following steps to resolve this problem:
Start up the software package while holding down the Shift key. This will prevent the Autoexec macro from running
If the database window is not displayed, press F11 to display it
From the Tools menu, select Options
Click on the Advanced tab, change the project name, and click Apply
Close the Options menu by clicking OK
Click the database Modules tab then select a module that you have design view permission for (such as CurrencyStuff) and click Design
From within Design view, select Debug, then Compile and Save All Modules
Close the module design window and then close down the application.
If you do not have Microsoft Access 97 loaded on your computer and you have not modified the software you can resolve this problem by downloading the sp27xx.exe (where xx represents the version number) file which contains the latest version of the Summit Pro 2000 software file with all modules already compiled from the Free Downloads page. If you have modified your Summit Pro 2000 software do not use this upgrade as it will overwrite any software changes you have made.