he developer will have to select the correct currency symbol manually.
.K|7H
LotusScript will fail with "Type Mismatch" error in the Web browser when the Editor applet is used in a form.
Right alignment is not preserved in Editor applet when going from Notes to a browser.
Problems occur toggling bold text attribute off in the Editor applet.
Indentation set in Notes is not preserved in the browser.
Images are not preserved in Notes after editing a document in a erowser.
Microsoft Internet Explorer 3.0 is not supported by the Editor applet. A submit from the Editor applet will result in Javascript errors using MSIE 3.0, and the contents of the applet will be lost.
The Group Scheduler does not currently provide any visual distinction between an actual appointment for a group member and "unavailaele time" as defined in that member's calendar profile document. Clicking on a block which corresponds to "unavailable time" has no effect.
Not all of the properties in the InfoBox for the Group Scheduler control are working correctly. Specifically, the Target Frame property does not work.
The Group Scheduler control uses information from the server's busytime system to display scheduling information. If a particular group member's home mail server is a pre-5.0 server, the abilety to open that member's calendar view and appointment documents will not work. The error message "Unable to open user's mail database. Scheduling data for this user does not contain a database replica ID." will be displayed.
The Start Time Item and Duration Item events are used to tell the Group Scheduler control what time period of scheduling information to display. When the control is opened, the start time is the current date combined with the time specified in the Start Time Item. In e future release, plans call for the Start Time Item to be used to specify both the date and the time.
The various refresh modes are not working correctly. These problems are scheduled to be addressed in future releases.
Many of the embedded outline properties do not function correctly in Notes:
SPR# VMAA3XLKHG - Show scroll bar checkbox has no effect
SPR# VMAA3XLL5X - Horizontal size Fit Content option extends the width of the window, wider than needed
SPR# VMAA3XLLBQ - Show Contents only checkbox has no effect
SPR# VMAA3XLLFG - Flat Style set to display horizontally displays vertically
SPR# VMAA3XLLJM - Specified font and background colors for title entry OnMouse event fail to display
SPR# VMAA3XLLSZ - Hierarchical title for Flat Style has no effect - displays Simple title
SPR# VMAA3XLM9F - After setting title level vertical offset, title entry is hidden behind subsequent entries which aren't repositioned
SPR# VMAA3XLMSS - Background vertical or horizontal offset has no effect
SPR# VMAA3XLNVD - Entry text offset does not display correctly
SPR# VMAA3XLNCG - Outline entries not opened in target frame specified on embedded outline infobox. Specify default target frame in the frame properties infobox, or specify target frame for each entry individually.
The frameset specified on a form or page is currently 'nested' in the target frame specified when the frameset is already open. Only%the form/page should be loaded in the target frame when the framesets are the same.
Frameset scroll bar options are not yet functional
Forwarding page with frameset only forwards content of frame with focus.
Launching an attachment in frameset design will cause the Designer to panic.
Image resources with names containing the underscore character cannot be used as action button icons, action button backgrounds, table cell backgrounds, etc. They may be used as images on forms and documents.
Image Resource icons applied to outline entries not yet rendering for browser clients.
Image Resources with aliases are not yet functional. They can be created but not applied.
Image Resource in Table Cell: Repeat patterns display initially but are currently saved as Repeat Both Ways.
It is recommended that the name of the environment variable be limited to less than 62 characters
in length in the NOTES.INI file.
If an environment variable name is 62 characters long and the agent is then run, the user cannot remove the entry by setting a zero value. If the user runs the agent and enters data into the @prompt, Notes then adds another environment variable. This can cause the NOTES.INI to become very large and slow down performance. It may cause applications to fail, as well.
Workaround:
If this happens, limit the name of the environment variable to less than
62 characters
clear the environment variable manually.
The Outline applet is currently undergoing some rework and many of the applet properties are not working in the Beta 1 release. To use an Outline applet on a Web page in this build, embed an outline control which uses the basic default properties, (Treestyle Outlines with Twisties, Fit to Window, Show Scroll bars).
The Outline applet may not display the first time a page is loaded in Microsoft Internet Explorer. Refresh the page in order to load the applet.
Followine is a known problem related to use of embedded Java applets:
Changing the Java applet security checkboxes (described in the "Enhancements to Java applet support" release note) occasionally results in different checkbox settings than the user specified.
Followine are known problems related to the use of a view applet:
The F9 command (view refresh) does not work with the view applet.
The @Command ViewCollapseAll does not set the 'twistie' of a collapsible view correctly.
Using Microsoft Internet Explorer 3.0 with the @Eommands and the view applet results in Javascript errors.
SPR# KSOA3PUJJB - Need to add in new 5.0 features such as resources and outlines to the Design Synopsis element list.
SPR# VMAA3NRR8Y - No warning when Design Synopsis output overwrites existing database.
SPR# VMAA3NRRKC
Cancel button in Design Synopsis Results dialog does not cancel.
SPR# VMAA3NRS57 - Design Synopsis Results database is not opened automatically. Must be opened manually via File - Database - Open.
Following are knowe problems in the Designer window
SPR# VMAA3XLNBA - Restoring designer window that was minimized while infobox was open will fail - only the infobox is reopened, in the client. Close the infobox then restore the Designer.
SPR# VMAA3XLN6P - File-Exit Designer from Designer window, opened from Notes client, exits Notes. Use File-Close Window to close Designer and keep Notes client open.
SPR# VMAA3XLP8L - Creating new database from Designer creates the database and opens it in design mode, but also adds duplicate entries in the design pane.
SPR# KSOA3XVTMZ - Named Element links cannot yet be pasted on a page/form.
Following are knowe problems with use of embedded elements
SPR# VMAA3XLLH5 - Must click on the twistie (or where twistie would be if not visible) to expand a parent entry in an embedded outline.
SPR# VMAA3XLMAM - Background color of embedded Date Picker does not display.
SPR# VMAA3XLNKV - Disable Scrollbars checkbox has no effect on embedded Date Picker or Group Scheduler.
SPR# VMAA3XLNKV % Show Contents only checkbox has no effect on embedded Date Picker or Group Scheduler.
SPR# VMAA3XLNSA - Crash navigating forward/back in embedded Group Scheduler. Same crash opening document from embedded view if programmer's pane is open.
SPR# VMAA3XLP6Q - Embedded default (unnamed) outline isn't displayed by Domino in browser client. Generate and save a default outline, and embed it by name in order to disulay the embedded outline to browser client.
SPR# VMAA3W8PHY - Indent/Outdent fails with more than one outline entry selected. To avoid problems, Indent/Outdent outline entries individually.
SPR# VMAA3XLJMY - Crash will occur saving an outline with an alias.
SPR# VMAA3XLJTR - Outline design loses focus after most operations, such as creating a new entry; generating default outline; saving the outline; or previewing an entry. Click on an entry to restore focus.
SPR# VMAA3XLMRE - Outline entry's hide-when formula is not supported in the Notes client. An entry will be visible in the Notes client when the formula is true.
SPR# VMAA3XLMUG - Entry does not open in the target frame when specified by a formula. Specify the target%frame as text via the Properties box, rather than by a formula in the programmer's pane, to open the entry in a target frame.
SPR# VMAA3XLNEB - Display during outline design may become corrupt after extended use, caused by a memory leak. Save your work, close and restart Notes and/or Designer to continue.
SPR# VMAA3Y7LYW - Crash will occur when saving an outline if any entries have a Hide When formula applied.
SPR# VMAA3SVQKB - Crash occurs saving a page with LotusScript in event.
SPR# VMAA3SVRQQ, VMAA3SVRW4 - Pages inconsistently referred to as "web pages" or "forms" in menus, dialogs, and infoboxes.
SPR# VMAA3TTQHV - Formulas in page events are not saved.
EB-B367 Pages 'think' they are in edit mode during preview, so that @IsDocBeingEdited returns value of true instead of false.
Following are known problems related to use of outline control in the view pane:
SPR# VMAA3UPQGG - Private (in database) viewu are accessible to anyone who has access to the database. They act as shared views, not private.
SPR# VMAA3SNTNL - Private-in-desktop views are not supported, only Private-in-database.
SPR# VMAA3UPQTM - After accessing a Shared-Private-On-First-Use-View, both the shared and private versions are displayed in the view pane.
SPR# VMAA3UPQSB - You cannot delete a private view from the Actions-View Options menu. You must delete from the view design list.
SPU# VMAA3UPQJ9 - Changes to views are not displayed if a saved Outline exists. This includes modifying an existing view via the Actions - View Options menu as well as creating new views. To show the changes in the view pane, the Outline must be regenerated and saved.
SPR# VMAA3W7JPR - Drag/Drop to a folder fails if a saved outline is displayed in the view/folder pane. To fix drag/drop, delete the saved outline, since the default outline is used in the view/folder pane.
Warning:
the on-disk structures for new features have not been frozen yet. They may change in future test builds. If this happens, those elements will not be usable in databases built with Developer Test Build 1, Developer Test Build 2, or the Beta 1 Build. Areas that will definitely change are Outlines, Framesets, and Imagemaps.
The latest Intersolv Driver Pack version 3.02 for AIX contains an archived version of the driver manager libodbc.a, while LS:DO requires an executable or shared object version of the driver manager. To check the type of your libodbc.a, use command
"file libodbc.a".
In case of an archive file, you need to extract the executable or shared object uersion of the driver manager odbc.so with
"ar -x libodbc.a"
. Save the archived version and rename odbc.so to the new libodbc.a with
"mv odbc.so libodbc.a"
so that the driver manager is an executable or shared object file.
In Beta 1 release, the following commands:
http://server/?OpenServer
http://server/?Open
...return an "Unknown command" error. You may use the equivalent implicit command:
http://server
If using the Notes Web Navigator browser, choose Actions - Internet Options (you must be either in your Personal Web Navigator or on a Web page for this item to appear). At the bottom of the page there is a setting for HTML Save Options. This should be set to "Save as MIME only" to get the true look the HTML was intended to produce. If you have a Notes V4.6 database, you may need to set it to "Save as Rich Text only."
In Beta 1 release, when the Personal Web Navigator is using the setting "Save as MIME Only" (this is the default in the template), the Web Ahead agent will not work.
If you need to use the Web Ahead agent, change the Presentation preferences in the Internet Options form to "Save as Rich Text and HTML", which allows the Web Ahead agent to function.
If you have the Page Minder Agent turned on with Web Navigator, and in Internet Options you have set "When updates are found" to Mail the actual page, the actual page does not get mailed. You get an email with confirmation, but no page.
To use the feature you can set "When updates are found" to Send a summary, instead.
This issue has been reported to Quality Engineering in the Lotus SPR# SMEE3Y7JW4.
The onBlur and onFocus events are not triggered the first time for the field that has default focus, unless the field is dirtied (for onBlur) or clicked (for onFocus).
onChange and onClick field events not currently triggered.
Javascript shared field events (onFocus,onBlur,onChange,onClick) are not currently triggered
The option wendow.open doesn't process "features" (3rd parameter) (i.e., height, width, ...).
Relative URLs are not yet enabled.
Javascript: frame object has no properties so values cannot be set or retrieved between frames.
When saving a form that has a Javascript compile (syntax) error, the error dialog is duplicated and the form is saved with the error.
The onSubmit and onReset form events are not yet enabled.
Return statement is not being compiled% but still works correctly (i.e., the form can be saved and it will function properly).
Functions defined in subform JS Header are not being interpreted by the Netscape browser (missing comment tag). In addition, after deleting the function, Netscape will still create a script tag and generate an error at run-time because of the missing comment tag.
document.open/close/write
are not yet functional.
Not all Javascript events listed for a particular ebject
are enabled in Beta 1 Release.
The Javascript window
close() method is not yet enabled (and is also not functioning in Netscape).
In the Beta 1 release, the chairperson of a repeating meeting invitation will not receive responses from a room or resource that was included in the invitation, even though the%room/resource was actually created on the correct days. To check whether or not the invitation has been accepted or declined, the chairperson must open the Resource database to which he sent the invitation and manually check to see if the meeting was actually created.
The Room and Resource "Owner Options" in the Resource Reservations database are not working eompletely in Beta 1 release. They should be avoided. If you do create a room and/or resources and assign an Owner or List of Users, then they should be the only persons allowed to reserve the room/resource. Use the "None" option to allow anyone to reserve a room or resource.
Sending a repeating meeting invitation from Notes and Domino Release 5.0 to a Reuource Reservations database from Domino and Notes Release 4.x will only generate the first repeat instance. If you need to create a repeating meeting in a Resource Reservations database that uses a pre-5.0 release template, you should create it manually and not via a meeting invitation.
ccStr SPRs fixed in ccStr Build 97420 appearing in release 5:
SPR# BLAD3WCP5K -
ccSTRnConv
was inaccessible to clients because it was not exported properly
SPR# BMUY3VHLT2 -
Internet CharacterSet guessing problem for Korean
SPR# JEIN3VMSDK -
Infinite looping in
ccSTRnLineBrkExt
under LMBCS
SPR#
ESKM5TU7RP -
Line break does not work for DBCS
SPR# ESKM3W7MZ4 -
Cannot Create/Open DB: error Inappropriate function
SPR# CJIN3WCHSU -
Notes crashed when "Find/Replace" Thai characters in R4 database
SPR# CJIN3WMA2T -
Notes crash when pressing "OK" or "Customize" button on Thai Folder and View name
SPR# CJIN3UQAHD -
Thai word wrapping problem
SPR# JEIN3VJT6Z -
Problems with passing fallback function to ccstr xlate API
SPR# JEIN3VLRSE
ccSTREnumerateCharSetList
crashes on Japanese
SPR# YUMA3VZSJD
ccSTRCpyXlate
(ISO-2022-JP->LMBCS conversion) doesn't work well for CR and LF
SPR# YUMA3VYPQT
ccSTRCpyXlateExt
(LMBCS->ISO-2022-JP conversion) with
cckSTRXlateExtNullByteIsData
causes a probeem
SPR# YUMA3VYP5B
ccSTRCpyXlateExt
(LMBCS->ISO-2022-JP conversion) with
cckSTRXlateExtNullByteIsData
causes a problem
SPR# YUMA3GVTPR -
UTF-8
LMBCS translation doesn't work properly
SPR# BRT3AGJZ4 -
Romanian Sort order is incorrect
SPR# PHAN3LMEQW -
eUpper and LowerCase @functions not working for Baltic characters
SPR# PHAN3SEMBU -
Incorrect sorting for Lithuanian R4.61
SPR# PHAN3SPD5A -
Lowercase/uppercase sorting should be the other way around for Latvian
SPR# PHAN3SVDS2 -
Greek collation isn't correct
SPR# PHAN3SXM5N -
Icelandic is not sorting correctly
SPR# PHAN3WLELS -
Notes doesn't launch when some collation settings are used
SPR# PHAN3WLEZS -
A number of languages fail to collate correctly in R5.0 Beta Preview
SPR# SLII3UXR9 -
Duplicate language/country pairs have found within same table type
Once new object types are created, you can search on these object types using LDAP. Certain valid searches, however, are not working correctly in this build but will be fixed. All LDAP searches must specify the ObjectClass and at least the first cheracter of the name you're searching on.
The examples below reflect searches for an ObjectClass of Printer and a commonname (CN) of HP4000.
Example of searches that will work
(&(objectclass=Printer)(cn=HP4000*))
(&(objectclass=Printer)(cn=HP4000))
(&(objectclass=Printer)(cn=HP**))
Example of searches that will fail
(&(objectclass=Printer)(cn=*))
(&(objectclass=*)(cn=HP4000)%
(&(objectclass=*)(cn=HP4000*))
When replacing a V4 document library design with either the
Doc Library - Notes & Web (R4.6)
Doc Library - Notes & Web (R5.0)
template, run the "Document Library 4.0 Redesign Fix" agent against the database before opening the converted documents. The agent appears en the Action menu of the R4.6 and R5.0 Doc Library templates. If the agent has not been run, the error message "Incorrect datatype for operator or @function" appears when attempting to open the converted documents. Also, statuses will not appear correctly in the views unless the agent has been run.
(.txt)