January 2000 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Release Notes for WebSPIRS v4.11 for SCO UNIX, Sun Solaris, AIX, NT, and Red Hat Linux =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- WebSPIRS 4.11 is the alternative language version of WebSPIRS 4.1, available in English, French, German, and Spanish. Apart from the alternative language interfaces, there is only one change to the software, correcting a bug, as described at section 5 below. Users of WebSPIRS 4.1 who are content with using the English-language version and do not require the bug fix do not need to upgrade to 4.11. ========================= About these Release Notes ========================= These Release Notes should be read together with the WebSPIRS v4.1 Administrator's Guide (which is applicable to WebSPIRS 4.1 and later releases). The guide is available in two formats: * A copy in PDF format is available from the ftp site: ftp.silverplatter.com/software/webspirs41/ws41adgd.pdf * A copy in HTML format is installed as part of the WebSPIRS installation package, and placed in the webspirs/url/doc/directory. You can view this document in a browser, starting with file wsig_toc.htm. Or you can get the document in either format from the SilverPlatter web site: http://www.silverplatter.com The WebSPIRS v4.1 Administrator's Guide (previously called the Implementor's Guide) has been re-written extensively for 4.1 onwards and contains full details of how to install and configure WebSPIRS 4.1 and later. You should download that document before you start to install WebSPIRS. These Release Notes contain the following additional information (along with other items listed in the Contents): * Any late-breaking information about WebSPIRS that has not yet been included in the WebSPIRS 4.1 Administrator's Guide. * Details of features that are new or are changed in this release. * Details of known issues in this release. Additional WebSPIRS Documentation --------------------------------- In addition to these release notes, and the Administrator's Guide, the following other items are available: * There is a short readme file, at /webspirs/bin/readme.txt, which is installed with the software. This file gives a brief summary of the user documentation available with WebSPIRS. * WebSPIRS online Help system: provides detailed,user-oriented information on searching with WebSPIRS 4.11. * WebSPIRS 4 QuickStart: shows users how to get started with basic WebSPIRS searching. You can find this guide (available in HTML and PDF) on SilverPlatter's web site (http://www.silverplatter.com). =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Contents =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 1. Downloading the software and the WebSPIRS Administrator's Guide 2. Requirements 3. Installing and Configuring WebSPIRS 4.11 4. Late-Breaking Information 5. New Features and Changes in this release 6. Known Issues 7. Contacting SilverPlatter Technical Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Downloading the software and the WebSPIRS 4.1 Administrator's Guide =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- If you have not yet got a copy of the WebSPIRS 4.11 software, and WebSPIRS Administrator's Guide, this is how you download them: Downloading the General Release software with a web browser: ------------------------------------------------------------ 1. Access the software download page on the SilverPlatter web site; http://www.silverplatter.com/support/registration.html 2. Choose the WebSPIRS 4.11 check box and select your platform from the drop-down menu. 3. Fill in the registration details, and click Submit Request. 4. The download package contains the following files: The compressed software (ws411), depending on the platform) These release notes (relnotes.txt) The Administrator's Guide, in PDF format (ws41adgd.pdf) Downloading the General Release software using ftp: --------------------------------------------------- 1. Use anonymous ftp to connect to SilverPlatter's site: ftp.silverplatter.com 2. Login with user-id anonymous and enter your email address as a password. 3. Change to the /software/webspirs directory. (To do this, enter cd/software/webspirs) 4. Change to directory for your platform (AIX, SCO, Solaris, Linux, or NT). 5. Make sure you will download the files as binary files. (To do this, enter bin) 6. Download all the files from the directory. (To do this, enter mget *. You are prompted to enter y to download each file.) The files will download into whatever is your local directory. The files are: The compressed software (ws411), depending on the platform) These release notes (relnotes.txt) The Administrator's Guide, in PDF format (ws41adgd.pdf) =-=-=-=-=-=-=-= 2. Requirements =-=-=-=-=-=-=-= Full details of the hardware requirements for installing and running WebSPIRS are given in the WebSPIRS 4.1 Administrator's Guide. Please also check the SilverPlatter web site: http://www.silverplatter.com/erl/erlgatewayreq.htm for any changes. The following is a summary of the requirements: * ERL 2.09.5 or higher * 10 MB of hard disk space * 2 MB RAM + 4 MB RAM per simultaneous user * A WebSPIRS-compatible browser: WebSPIRS 4.11 has been tested using browsers running on the following platforms: * Netscape Navigator 3.01 (32-bit) or higher for Windows 95, Windows 98, Windows NT (4.0 or higher), or Netscape 4.x or higher for the Macintosh. NOTE: We recommend Netscape 4.08 or later for a 68K Macintosh. * Microsoft Internet Explorer 4.0 (32-bit) or higher for Windows 95, Windows 98, or Windows NT (4.0 or higher) only. (IMPORTANT: Internet Explorer for the Macintosh is not a supported web browser.) To ensure optimal performance of the WebSPIRS 4.11 gateway, we recommend that it is used with browsers running on these platforms. You may experience problems using browsers on other platforms such as Windows 3.1 or X Windows. NOTE: The browser's JavaScript capabilities must be enabled at all times. Java must be enabled only if you subscribe to SilverPlatter full text databases that use the Table of Contents feature. NOTE: Because WebSPIRS 4.11 is not CGI-based, it does not require a separate web server to run. However, using WebSPIRS 4.11 will not prevent you from using your preferred web server for all your other web-based applications. * You will be asked to provide the following ERL server information during the WebSPIRS installation: * Hostname or IP address of the ERL server you want WebSPIRS to access. * (UNIX only) The user account name and group name that you want to own WebSPIRS. (You can use existing user account and group names or you can create new ones.) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 3. Installing and Configuring WebSPIRS 4.11 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This section covers the following important items: * Installing WebSPIRS * Making additional alternative language versions available to users * Changing the language used for the language check boxes * Changing the language in the Document Delivery forms Installing WebSPIRS =================== Details of how to install the WebSPIRS software are given in Chapter 4 of the WebSPIRS 4.1 Administrator's Guide (ws41adgd.pdf). This section contains the additional information you need if you want to install an alternative language version of WebSPIRS. When you start to install the 4.11 software, an additional question asks you to choose the English, French, German, or Spanish version as the preferred language. WebSPIRS installs all the language templates, using the language you selected as the default, so that starting WebSPIRS with the normal WebSPIRS URL: http://: accesses WebSPIRS in the language you specified. Making additional alternative language versions available to users ================================================================== The previous section explained how to set up a default language version. You can also make additional language versions available to specific users. There are two ways you can do this. You can use both methods on the same WebSPIRS installation. Method 1: Create a user-specific WebSPIRS configuration -------------------------------------------------------- This means that users all access WebSPIRS using the same URL, but the language they see is set according to their user name. Follow the instructions in the Administrator's Guide, Chapter 6 Configuring WebSPIRS: "Creating a User-Specific WebSPIRS Configuration Based on ERL Username" to set up a user-specific configuration. In each .cfg file you create, add an entry: www.connection.template_directory= adding the path to the template directory for the language you want that username to access. Method 2: Create a WebSPIRS configuration in a separate directory ------------------------------------------------------------------ This means that users access WebSPIRS using the specific URL for their chosen language. Follow the instructions in the Administrator's Guide, Chapter 6 Configuring WebSPIRS: "Creating a Special WebSPIRS Configuration" to set up a different configuration directory for each language you want users to access. In the webspirs_user.cfg file created in each directory, edit the entry: [WWW.CONNECTION] template_directory= adding the path to the template directory for the language you want to access. Your users access the chosen language using a URL formed like this: http://://? When you set up a new directory in this way, you automatically create a /docdeliv subdirectory within the new directory. This is not the /docdeliv directory you will use if you set up the Document Delivery feature, (as described below) so you can delete this new /docdeliv directory. Changing the language used for the language check boxes ======================================================= There are five language check boxes under the Find: prompt on the main WebSPIRS search page. Users select these if they want to find only those records that contain an entry in the language field (LA) that matches any of the languages they select. (Note that a check box is only displayed if the open databases contain at least one LA= field containing an entry for that language.) The labels for these check boxes are set in the [SP.LANGUAGE] section of webspirs_user.cfg. WebSPIRS displays the check boxes with labels in the language you specified as the default language when you installed WebSPIRS. If you set up WebSPIRS so that your users can access different language versions from a single WebSPIRS installation (by creating a user-specific configuration, or a configuration in a separate directory) you must enter some additional settings to display the check box labels in another language, as explained in the next sections. NOTE for either method ---------------------- You must include the options that use the English language names (option1.p=English, option2.p=French, and so on) because those are the names that are used in the LA= field in the databases. * If you are setting up a user-specific configuration ----------------------------------------------------- Add a section to each .cfg you create, based on the following example which displays the boxes with French labels: [SP.LANGUAGE] option1.p=English option2.p=French option3.p=Spanish option4.p=German option5.p=Italian option1.name.p=anglais option2.name.p=francais option3.name.p=espagnol option4.name.p=allemand option5.name.p=italien * If you are setting up a configuration in a separate directory --------------------------------------------------------------- Edit the [SP.LANGUAGE] section of webspirs_user.cfg, based on the following example which displays the boxes with French labels: {SP.LANGUAGE] option1.p=English option2.p=French option3.p=Spanish option4.p=German option5.p=Italian option1.name.p=anglais option2.name.p=francais option3.name.p=espagnol option4.name.p=allemand option5.name.p=italien Changing the language in the Document Delivery forms ==================================================== The steps you need to follow to enable document delivery vary depending on the type of installation you have selected. If you have chosen to provide more than one language by creating subdirectories in the /bin directory and creating a webspirs_user.cfg file in each subdirectory (as set out at Method 2 in the above section: "Making additional alternative language versions available to users"): All you need to do is enable document delivery in each webspirs_user.cfg file, by adding the following: [DD] root.spec.directory.p=./docdeliv_x where "x" is one of f, g or s, depending on the language required. (Or just "docdeliv" for the English language version.) To nominate a single document delivery service, add the following entry to the DD section: provider.show.exclusive.p=provider.cfg where "provider.cfg" is one of ill.cfg, bl.cfg or cisti.cfg. If you have chosen to provide more than one language by creating username.cfg files in the /bin directory (as set out at Method 1 in the above section: "Making additional alternative language versions available to users": 1. Enable document delivery for the user by editing the username.cfg file in the /bin directory to contain the following: root.spec.directory.p=./docdeliv_x where "x" is one of f, g or s, depending on the language required. (Or just "docdeliv" for the English language version.) 2. Create a directory with that username in the users subdirectory of the relevant docdeliv directory. For example, for a French-speaking user called Claudette, you would have a file claudette.cfg in the /bin directory, and a directory claudette in the docdeliv_f/users subdirectory. 3. Copy the relevant providers files (ill.cfg, bl.cfg and cisti.cfg) from the relevant docdeliv/providers subdirectory to the directory for that username in the users directory. In our example, you would copy the providers files from the docdeliv_f/providers subdirectory, to the docdeliv_f/users/claudette subdirectory. Adjusting the browser window size ================================= Users of the French, German, or Spanish versions may notice some clipping of the contents by the browser window, particularly if they have chosen "large fonts" in their Windows settings, or have large fonts selected in their browsers. They can enlarge the window manually to overcome this problem, or change their fonts settings to "small fonts". Alternatively, you can change the default window size, which is set in webspirs\bin\theme.cfg. The current settings in theme.cfg are: [SP.WINDOW] width.p=620 height.p=400 Any settings in theme.cfg override the ones in webspirs_user.cfg =-=-=-=-=-=-=-=-=-=-=-=-=-=- 4. Late-Breaking Information =-=-=-=-=-=-=-=-=-=-=-=-=-=- Addition to the Administrators Guide ------------------------------------ Chapter 6 Add at page 6-10 of PDF version, after section on Auto-Opening Databases: Jump-starting users into WebSPIRS --------------------------------- Summary ------- You can create a URL so that your users can open WebSPIRS with specific databases open, ready for searching, without using the login and database selection pages. You could attach this URL to a link from a web page, so that users can move easily from your library intranet, for example, to using WebSPIRS. What you do ----------- To create the URL, you combine server, login, and database information (linked with an ampersand "&") to create a URL like this: http://:/?sp.username=&sp.password= &sp.form.first.p=srchmain.htm&sp.dbid.p=S(ML) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 5. New Features and Changes in WebSPIRS 4.11 General Release =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= (Some of these changes were reported in the release notes for earlier beta releases) Searches started in the Search Builder now obey Publication Year limits ----------------------------------------------------------------------- (10578) A bug whereby searches started in the Search Builder ignored any Publication Year (PY) limits set on the Set Other Limits page has been fixed. A number of performance issues have been addressed since the beta 3 release. Users of browsers other than Netscape 3 will notice an improvement in the procedure for printing records in WebSPIRS 4.1 and later: in particular the number of steps has been reduced, and users no longer see the extra javascript messages that previously appeared in some browsers. ---------------------------- Changes Since WebSPIRS 4.1B1 ---------------------------- 1. Overall performance has been improved, with gains ranging from 20% to 60%, the greatest improvement being experienced by those connecting over a modem or over a heavily loaded network. The performance improvement have been achieved in a number of ways: (1) Optimization of the JavaScript used in the WebSPIRS pages, resulting in a significant reduction in the amount of data transferred across all WebSPIRS 4 operations. (2) The introduction of threading when reading/writing to the network. (3) Optimization of string handling when processing templates. 2. The "pausing problem", which was determined to be caused by slow connections causing all other requests to get backed up, has been fixed. This problem would have appeared to users as delays of some number of minutes between an operation being submitted and a response being received by the user, sometimes described as WebSPIRS hanging. 3. A memory leakage problem associated with Netscape 4, which resulted in severe system slowdown and eventual hanging after 10-15 successive searches, has been resolved 4. A condition resulting in runaway WebSPIRS processes has been resolved. 5. Links to the BIBSYS service ------------------------------ Members of participating libraries can link to BIBSYS to request loans or article copies. This facility is initially available only with SilverPlatter's Medline databases. When BIBSYS links are enabled, a hotlink of the form "ORDER from BIBSYS" displays under each Medline record. Clicking on this link opens a browser window to the BIBSYS system, preset with the bibliographic details from the record. Users are prompted for a BIBSYS Patron ID and password. You enable the links to the BIBSYS service by making the appropriate settings in the webspirs_user.cfg configuration file: 1. Open the file webspirs_user.cfg in a text editor, and locate the [SP.ILL] section. 2. Edit the enableBibsys line: To enable links to BIBSYS edit the line to read: enableBibsys=1 To disable the links edit the line to read: enableBibsys=0 3. Edit the bibsysLang line to set the language of the BIBSYS interface to English or Norwegian: For English, edit the line to read: bibsysLang=?lang=E For Norwegian, edit the line to read: bibsysLang=?lang=N 4. At the bibsysPrompt line, you can change the wording of the hotlink, by changing the default wording "ORDER from BIBSYS". 5. Save and close the file. 6. Links to the Pica service ------------------------------ Members of participating libraries can link to Pica to request loans or article copies. This facility is initially available only with SilverPlatter's Medline databases. When Pica links are enabled, a hotlink of the form "Bestel via PiCarta - NCC" displays under each Medline record. Clicking on this link opens a browser window to the Pica system, preset with the bibliographic details from the record. Users are prompted for a Pica Patron ID and password. You enable the links to the Pica service by making the appropriate settings in the webspirs_user.cfg configuration file: 1. Open the file webspirs_user.cfg in a text editor, and locate the [SP.ILL] section. 2. Edit the enablePica line: To enable links to Pica edit the line to read: enablePica=1 To disable the links edit the line to read: enablePica=0 3. Edit part of the line picaURL2Lang=/LNG=EN/CMD?ACT=SRCH&TRM= to set the language of the Pica interface to English or Dutch: For English, edit the LNG part of the line to read: LNG=EN For Dutch, edit the LNG part of the line to read: LNG=NE 4. At the picaPrompt line, you can change the wording of the hotlink, by changing the default wording "Bestel via PiCarta-NCC". 5. Save and close the file. --------------------------------------------------- Problems Corrected in WebSPIRS 4.1 General Release: --------------------------------------------------- * ERL Send Message feature now works with WebSPIRS 4.1 and later (8908) * General Index terms now search the correct index (9302, 8299) * PY (Publication Year) setting is now displayed on the Search page when set in the Limit your Search page (9307) * SDIs now work on NT (9403) * Using a saved search history gives correct results (9487) BUT please note that search histories created in versions of WebSPIRS earlier than this release, and which gave incorrect results, must be re-entered, and run, and saved again. * Clicking on terms in Suggest page now has consistent results (9545) * The table of Contents feature now allows you to switch between Table of Contents (9574) * Resizing windows on a Mac now displays correctly (9608) * The problem where if one of two or more listed ERL servers is shut down, users cannot access databases, has been solved (9626) * When used in conjunction with ERL dbserver v4.05 or later, searches for the same name genus-species (such as gorilla gorilla) now retrieve only those records which contain instances of the tow identical terms adjacent to one another. (9855) * Single-word journal titles or single-word descriptor terms may now be retrieved by typing in the term, followed by a hyphen, in SilverPlatter databases that support this feature. * Alerts now work on UNIX platforms. (9402) * Changing the email address for a search history no longer overwrites existing histories. (9861) * The problem whereby hotlinks to holdings in HCU messages had a limitation on the length of the URL has been fixed. (9451) * For certain databases (for example, INSPEC, BACD), records were not sorted in the reverse chronological order that users expected. The order in which records are displayed is now determined by the order in which they are presented for display by the dbserver, as is the case with WinSPIRS. (9597) * We have included new scripts to run SDIs. This means that SDIs are only re-run when done so by the System Administrator (or at a regular time the administrator sets). This is documented in Chapter 6 of the Administrator's Guide - Configuring WebSPIRS - Enabling SDIs. Users can no longer set the frequency of SDIs. This solves a problem caused when multiple database licenses are needed to run SDIs at the same time. It also means administrators can decide only to run SDIs when they have updated their databases. =-=-=-=-=-=-=-= 6. Known Issues =-=-=-=-=-=-=-= The following issues and bugs have been identified in WebSPIRS 4.1 and are applicable to 4.11: * Index term list may display inconsistently if you switch Indexes: ----------------------------------------------------------------- (8135) If you switch indexes on the Index page without typing a term in the Term: field first, the term list at the bottom of the page may scroll to a random section of the Index instead of showing you the first term. SOLUTION: Always type a term in the Term: field before switching to another index. * Maximizing a window displaying records in Netscape 3 displays ------------------------------------------------------------- incorrect records: (9538) ---------------- If a user who is using Netscape 3 carries out a search, scrolls to, say, record #40 of 50, and maximizes the display window, the displayed records revert to the first record. * WebSPIRS in IE does not recover when the ERL times out: (9599) ------------------------------------------------------- If you leave an open WebSPIRS sessions inactive for so long that the ERL server times out, WebSPIRS does not recover, and IE reports that it cannot open the internet site, even when you try to log out. SOLUTION: We encourage users to save their search histories, and log out, if they will be leaving WebSPIRS inactive for longer than the time out setting. * Problems with running saved SDIs: (9628) -------------------------------- We are aware of problems loading and running saved SDIs from a workstation. ("Load" runs the SDI, and "Run" loads it.) * Search histories need re-creating: --------------------------------- Search Histories that were created before this release, and which gave incorrect results when they were re-run, must be re-entered, and run, and saved again. * 12 EC_BADKEY DBHANDLE error seen by the browser: (9762) ----------------------------------------------- We have received reports of an error message occasionally appearing in a browser, or in the WebSPIRS log, referring to EC_BADKEY DBHANDLE, but we have not yet found the precise circumstances in which it occurs. * Cannot use Internet Explorer to create SDIs from WinSPIRS: (10009) --------------------------------------------------------- System Administrators using WebSPIRS to allow WinSPIRS users to create and run SDIs should note that SDIs cannot be created from WinSPIRS if WebSPIRS is running in Internet Explorer. * Account names for search histories are case sensitive: (10202) -------------------------------------------------------------- WebSPIRS does not distinguish between lower and upper case letters during login. However, the account name attached to a search history is case sensitive. That means a user sees only the search histories for the account name that has the same lower and upper case letters that the user entered when they logged in for the session during which they created those search histories. * Problem saving marked records ----------------------------- We have had reports that if a user chooses to save all marked records, the resulting file is empty. SOLUTION: This problem does not occur if the latest version of the ERL server software, version 4.05, is installed. * Suggest Button not always available with INSPEC database: (10261) ----------------------------------------------------------------- Incorrect tags in certain segments of the INSPEC database (covering the years 1985-89, 1990-97, and 1993-94) mean that these segments are not recognized in WebSPIRS as belonging to the INSPEC database family. This means that if a user opens one of these segments together with other INSPEC segments, the Suggest button is not available. * WebSPIRS running on Solaris v2.5 cannot display links to -------------------------------------------------------- electronic journals: (10167) ---------------------------- WebSPIRS running on Solaris v2.5 cannot display SilverLinker links to full text journals. WebSPIRS must be running on either Solaris v2.6 or Solaris v7 to display these links. * Intermittent problem with document delivery (10423) --------------------------------------------------- We are aware of an intermittent problem with document delivery, in certain circumstances. If you have enabled library holdings, and you have configured the British Library or ILL document delivery service, and a user searches the MEDLINE Advanced database, the "Order" button for document delivery does not always appear next to all the records in the Retrieved Records display.(If your document delivery configuration includes the CISTI service, users see the "Order" button, but only see the CISTI order form.) SOLUTION: If your user selects "Complete Record" from the Change Display Options screen, the "Order" button appears in the Retrieved Records display correctly. If your user subsequently changes the display options, to reduce the number of fields displayed, the "Order" button still appears. * Problem with printing SilverLinker links (10319) --------------------------------------------------------- We are aware of a problem that when printing records in Netscape that contain SilverLinker links to full-text articles, the printing can out out with very small fonts. This happens when SilverLinker links are configured to appear in a drop-down menu. SOLUTION: * Users can de-select the FTXT field from the fields they want to print, before printing the records. * Administrators can make either of the following changes to the webspirs_user.cfg file. * Set SP.SILVERLINKER.format=TEXT (this ensures full-text links always appear as text links). Or, * Set SP.SILVERLINKER.format.select.min=4 (full=text links will only appear in a drop-down menu if there are 4 or more links for any one record.) * Publication Year now switched off on the Search Screen by default ----------------------------------------------------------------- (10519) The setting to show the Publication Year limit boxes on the main Search screen is configurable. This is now switched off by default, and improves WebSPIRS performance when searching many databases at once. Users can limit their search according to publication years by using the Set Other Limits screen. If you wish to display the Publication Year limit boxes on the main Search screen, set the following setting in webspirs_user.cfg: search.show.py.limits.p=1 * Using the Back button after a "jumpstart" into WebSPIRS (10530) -------------------------------------------------------- If a user connects to WebSPIRS by a jumpstart, then closes WebSPIRS, and clicks on the Back button, they see a WebSPIRS message about "Zero hits in all databases". The correct way to return to the previous WebSPIRS session is as follows: IE - Right-mouse click on the Back button, or click on the downwards pointing arrow next to the button, then select the WebSPIRS session from the drop-down menu. Netscape - Right-mouse click on the Back button, then select the WebSPIRS session from the drop-down menu. * Error message may appear when searching the Thesaurus on Linux with IE ---------------------------------------------------------------------- 4.0: (10553) ---- We are aware that if a user selects a large number of terms in the Thesaurus, when using WebSPIRS on Linux with IE 4.0, they may see an error message saying that IE cannot open the relevant Internet site, and that the connection with the server was reset. In fact, the search does take place, and if the user clicks OK on the message box, they can proceed. * HTML error when clicking on printing help in Spanish (10757) ---------------------------------------------------- If you click on the help icon when using the Print functionality in Spanish you may receive an html error message, although the help displays correctly. * HTML error on deleting an Alert (10756) ------------------------------- If you delete an Alert you may see an HTML error, although you can continue after this. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 7. Contacting SilverPlatter Technical Support =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you need further assistance with the WebSPIRS software, please send an e-mail to support@silverplatter.com or contact one of SilverPlatter's regional offices: UNITED STATES: SilverPlatter Information, Inc. 100 River Ridge Drive Norwood, MA 02062 Tel: 800-343-0064 781-769-2599 Fax: 781-769-8763 ---------------------------------- LONDON: SilverPlatter Information Ltd Merlin House, 20 Belmont Terrace Chiswick, London W4 5UG England Tel: +44 (0) 20-8585 6400 Fax: +44 (0) 20-8585 6640 ---------------------------------- AMSTERDAM: SilverPlatter Information BV Nieuwe Herengracht 49 1011 RN Amsterdam The Netherlands Tel: +31 (0)20-625 96 50 Fax: +31 (0)20-623 74 08 ---------------------------------- BERLIN: SilverPlatter Information GmbH Guentzelstrasse 63 D-10717 Berlin Germany Tel: +49 (0)30-857799-0 Fax: +49 (0)30-857799-99 ----------------------------------