BUG: Links displayed in the right-click menu are converted to lower case.

Description:
After creating a link gem that points to a web site/page using upper case characters in the URL, attempts to access the url using the right-click menu from Gem View fail on servers that are case-sensitive. This occurs due to an erroneous case-conversion when the menu is displayed - the link is actually stored properly in the database.

Workaround:
If you suspect one of your URLs is not working for this reason, open the gem and click on the link in the 'View' tab - it is correctly displayed here.

Status:
This bug will be fixed in an upcoming maintenance release.

BUG: Clicking a link gem that points to a folder causes error.

Description:
After creating a link gem that points to a folder on a hard disk or network server, if the gem is subsequently opened and the link clicked, an error indicating the link is no longer available appears, even though the link is still valid. Links pointing to files or web pages are NOT affected.

Workaround:
Users of version 1.12 can use the 'right-click' menu displayed by gems in the tree view to follow links. This does not trigger the error.

Status:
This bug has been fixed in the 1.12.16 Maintenance Release.

BUG: Text placed in the 'Notes' section of a gem is truncated.

Description:
When adding notes to a gem using the 'Notes' field on the Gem Properties dialog, the field will allow any amount of text to be typed or pasted in. However, upon saving, all but the first 255 characters are lost without any warning to the user.

Workaround:
This bug is caused by a hidden hard-limit on notes of 255 characters that were erroneously left in the product. There is no current workaround for this error.

Status:
This bug has been fixed in the 1.12.16 Maintenance Release.

BUG: Exporting all or part of a database into itself should not be allowed, but works anyway, causing duplication.

Description:
When using the export wizard, you can select the gem database from which you are exporting as the target database. Although an error message warns that this is not allowed, you can proceed with the export, resulting in duplicate entries in the database.

Workaround:
This bug does not trigger serious or fatal errors within the program, however, you should always make sure to select a new, or existing target database different from the one you are exporting from.

Status:
This bug has been fixed in the 1.12.16 Maintenance Release.

Description:
When using the export wizard, you can select to export to a new database file. If the subsequent dialog windows, which request additional information, are canceled, a message reporting an 'Unexpected Error' is displayed. The details report a 'File not found' error.

Workaround:
This bug does not trigger serious or fatal errors within the program, and the export wizard may be canceled or resumed without further errors.

Status:
This bug has been fixed in the 1.12.16 Maintenance Release.

eGems Collector Version 1.0/1.1

BUG: Dragging a gem from Gem View onto the desktop, Windows Explorer or application expecting file data causes 'Unexpected Error'. The detail reports error number 76 'Path Not Found.'

Description:
This error only occurs if the gem name contains leading blank spaces or is entirely blank spaces. Several actions can result in gems with leading blank space in the gem name or names that are entirely blank spaces. When naming or renaming gems, a leading blank space can be introduced accidentally. When dragging or copying blank spaces to create a gem, a gem can be saved with a blank name.

Workaround:
If you experience this error, examine the offending gem closely. Make sure that it has a valid name with no leading blank space. Rename the gem if needed and try the operation again.

Status:
This bug has been fixed in the 1.1 Maintenance Release.

ISSUE: Users infected with the 'I Love You' virus or its variants may not be able to start eGems Collector. Starting the program may cause Error 53 - 'Unable to Load Splash.jpg' and the program will not start.

Description:
This virus strain attacks media files, specifically jpeg images, which are used to display graphics in the eGems program. Since the virus removes these files from the user's system, eGems cannot find them on startup and the program will not continue.

Workaround:
The most important step in solving this problem is to eradicate the virus infection using an anti-virus program with virus definitions dated May 4th at 3:00 PM (Pacific Time) or later. See http://www.mcafee.com for more information. After your system is clean, you may reinstall eGems to restore the lost files or, if you prefer, follow the instructions below:

Download the files in gemjpgs.zip (you will need a zip utility like WinZip or PKzip), open it and extract the two enclosed jpg files into the following directory under the directory you installed eGems in:
Install drive and directory\gemteq\egems\Media - For example, if you chose the defaults, this would be: c:\program files\gemteq\egems\media\.

Description:
Because eGems uses zip compression to save space in its database, it will create temporary files in the zip file format when opening or saving compressed items. The utility causes these files to behave as if they were folders, thus hiding them from the program and resulting in the 'file not found' error.

Workaround:
Disabling the zip file utility will cause eGems to function normally. Users who wish to use the utility and eGems simultaneously may choose to disable compression in eGems by clearing the 'Compress gems...' item in the Options dialog. Note: This will result in all newly created gems opening normally, but will not allow previously compressed gems to be opened. In addition, this change may result in a significant increase in disk usage.

Status:
The usage of zip compression within the eGems program is by design.

BUG: Dragging and dropping data from Excel, Eudora, or other programs that support HTML clipboard data onto eGems Collector causes the program to terminate with multiple error messages.

Description:
This is the result of an error in handling data provided by source applications in HTML format. Dragging data as described above directly onto the eGems logo in the toolbar results in an 'Invalid Procedure Call' error, the logo displays a cross-hatched pattern of lines, and the program must be stopped and restarted in order to resume functioning. Dragging the data onto 'Chest' or 'Tray' items in the Gem View results in an 'Unexpected Error'. The detail reports an 'Invalid Procedure Call', but the program continues to function.

Workaround:
With source applications that trigger this error, use copy and paste to create gems. Copy and paste does not trigger this problem.

Status:
This bug has been fixed in the 1.1 Maintenance Release.
Also be sure to check out the eGems FAQ for the latest tips and workarounds.