There is a complete list of error messages and diagnostics in alphabetical order here.

Please send us an email giving the full text of the error message (cut and paste the message or send a screenshot if you can). We also request additional details as described in Reporting Problems.

We do not store your passwords, so we must request you to send a file from the server which we can analyze. Use PKZip or WinZip to compress the MWebUni.dat file, then attach it to an email to info@systemsplanning.com and we will recover the password. (In order to avoid spam filtering, use the word MWeb in the subject line.)

In order to verify that you are the Project Owner, you must provide the MWeb order number and the credit-card number originally used to purchase MWeb. Because of the time it takes to recover your password, we reserve the right to bill $30.00 for repeated requests.

Here is the procedure:

1. Go to http://store.esellerate.net/support
2. Enter your email address and your order number and log on
3. If you are a beta tester, enter our Webstore logon and password
4. Click the here link under the Re-download section to view your original receipt
5. Click the yellow and black Download Now button

Then use the normal installation procedure with the downloaded file.

We do not use product activation, so this means that some link has gone wrong. Follow the instructions in the previous item to re-download.

If there is a popup logon box it is from IIS, not from MWeb. This means that the program has the wrong permissions. See the subsection "Setting permissions on physical directories" here.

If you are using Windows Server 2003, you may need to set the Web Service Extensions to allow executable programs to run. See the installation instructions for this procedure.

For MWeb Enterprise and PastPerfect-Online databases, MWeb Universal uses the configuration and index of the original database. Changes made in Universal would not be sent to the original database because this would affect the other users of that database. Therefore, make required configuration changes to the original database.

This is done so the display will wrap and not be too wide. The spaces are inserted for display purposes only and do not affect your Database.

A limitation of the Microsoft Visual FoxPro ODBC driver means that the wizard cannot fill the list of tables if the FoxPro database is a DBC; you will have to add each table by hand. If possible, use free tables to avoid this problem.

Indexing may fail if the incorrect Encoding is set.

Normally indexing takes a few minutes, up to a few hours for a large database. The status report in your browser should change periodically as the indexer works its way through the Database. If there is no change overnight, click the Stop button in the browser and notify Systems Planning. For MARC files, make sure the files adhere strictly to the format.

We have optimized the indexing process as much as possible. However, there are things you can do. Most important, eliminate unimportant tables and fields from the indexing. Do this by clicking the Configure button for the Database, selecting Configure Tables and unchecking the Use This Table checkbox for unimportant tables. Then click Configure Fields and uncheck the Use This Field checkbox for unimportant fields.

A future release of MWeb will allow you to reindex only tables that have changed rather than the entire Database. However, if most of the tables have changed, it will still be faster to reindex the entire Database.

If you did not export some tables in the PastPerfect web-export wizard, go to the MWeb Universal Configure Tables display and uncheck the tables you did not export, then reindex

Please see the section on Performance

Searches are not case-sensitive in MWeb. There is no way to specify this. You may enter search terms in any case you wish and the results will be the same.

Searching the Leader and Fixed Fields is not really practical. MWeb limits a keyword in its index to 15 characters. Therefore whatever you enter as a search term, only the first 15 characters will be matched. In addition, the MWeb index is a keyword index, so you cannot use embedded spaces in a search term.

MWeb's keyword index stores values as single words, without spaces. Therefore a pair of indicators like " 4" is stored as "4". This means you cannot search for indicators containing a space. This capability may be added in a later release.

Subfield delimiters are considered to be word-separators in MWeb. Therefore each subfield is treated as one or more words and put into the index separately. You cannot specify the subfield to be searched. However, you may use phrase searching to span the subfields. For example, you can search for "smith john 1919" using the quotation marks and you will get the 1xx subfields $a and $d if they are adjacent in the MARC record.

The MWeb Universal Data Connectors return data from your Databases in XML. The field labels become XML element names (the names between the < and the >), and these are not allowed to contain ampersands or number signs. Therefore the Data Connectors replace ampersands (&) with the word "and", and number signs (#) by the word "Number".

This symbol is displayed by MWeb when it has detected an invalid UTF-8 code. Invalid codes will cause display problems, so this symbol (called a Geta) is used instead. This substitution is just for display -- your original data is not modified in any way.

Three data elements control what fields are displayed:

- the Use This Table checkbox in Configure Tables must be checked for any of the fields in the table to be used in the Project

- the Use This Field checkbox in Configure Fields must be checked for the field to be used in the Project

- finally, the field must be assigned a display sequence number for it to be displayed. The display sequence number used depends on what kind of display is being shown. The Data Display Sequence field controls the Search Results data layout, the Thumbnail Display Sequence field controls the Search Results thumbnail layout, and the Full Record Sequence field controls the Full Record layout.

In other words, make sure that the table has Use This Table checked, and that some fields have both their Use This Field checkbox checked, and also have a display sequence number that is not zero. (Incidentally, the three display sequence numbers also control the order the fields are displayed.)

The table in question may have a primary key made up from multiple fields in the table. Logon as the Administrator and click the Databases button and go to Configure Tables to correct this.

At present, MWeb Universal has a limit of 60,000 characters per field. Please contact Systems Planning if this is a problem

Some browsers, such as Firefox 2.0, do not display UTF-8 combining diacritics correctly. Others, such as IE7, show the data correctly. This is a problem when diacritics are stored as separate characters, such as in MARC files.

Unfortunately Internet Explorer 6 does not implement this feature correctly (Internet Explorer 7, Firefox, and Safari handle it correctly). Instead, it is necessary to insert a &nbsp; (non-breaking space character) into each empty cell. To do this, change the relevant XSLT stylesheet from

     <td><xsl:apply-templates /></td> 

to

     <xsl:choose>
          <xsl:when test=normalize-space(.)>
               <td><xsl:apply-templates /></td>
          </xsl:when>
          <xsl:otherwise>
               <td>&nbsp;</td>
          </xsl:otherwise>
     </xsl:choose> 

This will have no adverse effect on other browsers.

If you see a pseudo-image that browsers show when they can't find an image, right-click on it and select Properties to see where the MWeb believes the image should be.