Additional Information About Enterprise Developer Release 1.1

This README file contains information about enhancements to the 
software and corrections to the printed materials.  We appreciate your 
feedback, please share your suggestions for improving our product or 
documentation.

This README contains the following sections
	INFORMATION SOURCES
	REPOSITORY
	DATABASES
	FORMS
	DATA ENTRY
	STYLES
	SCALESCRIPT
	REPORTS
	CHARTS
	MISCELLANEOUS
	
=======================================
INFORMATION SOURCES
=======================================

DOCUMENTATION and HELP
The Release 1.1 booklet is an addendum to the original documentation.  
The help system has been updated to reflect changes for release 1.1.

SUPPORT
Symantec provides 90 days of free support, beginning at the date of your 
first call.  Our support number is (503) 984-7860.  

Electronic support is available through the Symantec bulletin board and 
the Symantec forums on CompuServe and America Online.

Additional information on Symantec's free and fee based support 
options is available in the back of the User's Guide and from the Help 
System.

TECHNICAL TIPS
The Help system contains an extensive Tech Tips section describing 
short cuts and "tricks of the trade" for Enterprise Developer.  If you 
uncover your own tech tips please send them to Symantec so that we can 
include them in future releases of Enterprise Developer.


=======================================
REPOSITORY
=======================================
	
FixedDec, VARtext, Boolean, LargeBinary are not recognized as 
reserved words. 

An attribute marked for deletion can not be undeleted.
	
Deleting an attribute deletes any relationships based on that attribute. 
Modifying an attribute to cause the dropping of a key will not delete 
relationships based on those keys.
		
Reserved words should not be used for attribute names (i.e. text, int, 
etc.)

Relationships cannot reference LargeText or LargeBinary attributes.

The name of key-based relationship can not be changed.
	
DEFAULT values are not reverse engineered.
	
Pre-existing rules and defaults on tables are lost when an "reverse 
engineered" entity takes ownership and executes a table re-organization.
	
An index placed on a datetime attribute forces the default datetime 
format.  The attribute dialog will maintain the original format.
	
Using a non-datetime field in dateconvert (), dateadd(), datediff() and 
datename() functions in the BRL will not display an error message.
	
The database link refresh operation is canceled if the operation attempts 
to refresh an open entity.

To substitute a choice attribute first delete the choice and refresh the 
entity.  Then add the new choice.  The refresh will not detect changes to 
a choice list if the total number of choices remains constant.
	
Privileges granted for Sequence objects are not maintained after table 
reorganization.                                    

There is a 32k size limit for E-R Diagrams.
	
The repository import operation will overwrite pre-existing forms, 
applications and entities with the same name without prompting the user.
	
During database link refresh, a table that already exists in the repository 
as an entity must be renamed.
	
Enterprise Developer does not reverse engineer rules and defaults on 
tables during the synchronize entity process.
	
The password protect when minimized dialog only allows 8 characters to 
be entered.  Enterprise Developer supports password up to 14 chars.

When creating an index, the name of the index must be filled in first.
	
The Business Manager tool bar's Relationship button's  help should read 
"Create a New Relationship"

Clustered non-unique indexes are not supported.
	
A primary key must also be flagged as unique in order to create a 
clustered index.  The repository will continue to indicate the clustered 
index Enterprise Developer does not create the associated index as 
clustered unless the field is flagged as required.
	
Attempting to create a new repository with an invalid login and then 
supplying a correct login with a different user name will fail during the 
create the repository operation.

	
=======================================
DATABASE
=======================================

XDB repositories must be on the same drive as the XDB database 
engine.

A second repository cannot be created in the same XDB location.

XDB Synonyms are not recognized in Enterprise Developer.
	
The Oracle data links do not support connections over SQL*Net Version 
2.0
		
Repositories created in Oracle using one network protocol must be 
accessed with that protocol.
			
Attempting to  log onto a Sybase database, via a data link, with an 
incorrect ID/password creates a "NULL DBPROCESS pointer 
encountered" message.
	
The user SA or any alias of SA  can not be added to and access a 
repository.


=======================================	
FORMS
=======================================

Viewing an attribute definition from the form builder always assumes 
the attribute definition has been changed.  If the attribute definitions 
have not been changed, click "No".

High ASCII characters can not be used as hot keys, they may be used as 
short cut keys.
	
The highest level on a custom menu that is initially grayed can not be 
ungrayed.

A BMP created using 256 colors will not display as a custom "BMP" 
button on a custom toolbar on a 16 color system.
	
Non-data connected radio, combo, and simple lists do not display a 
name.  The name is visible through a right mouse click.

Static objects are not carried forward when the layout is automatically 
redrawn by Enterprise Developer.

If a form is brought up as a ChildForm in a ChildWindow, it will display 
a Black Border unless Form.Fill is changed and Record.Fill is changed. 

A child window object on a form that does not have a form opened 
inside it, will be painted on top of all other objects.
	
Object-specific help for a child window cannot be accessed at run time.
 
The Last Record button and menu item are not activated until the last 
record in the form has been selected, either by a script or by selecting 
Next Record and going to the end.

The form errorhandler does not fire or receive control when entering 
incorrect data for a field. An error message box does fire.

A custom list can not have a greater number of choices than the 
underlying field.  If the number of choices exceeds the number of 
underlying fields the excess choices will not be selectable.

Descending order sorts on grouped fields are not supported on browse or 
print report forms.

The "New record after save" property from the form usage dialog will 
not be invoked by F8 - Save a new Record.  A new record is only 
displayed after using F2 - Save as new.
	
Lookup can not be used for Entity Filter criteria during form run.
	
An  Entity Filter can not be set for a Group By on a subform.
	
Bitmap paths are not stored as part of pre-placed style objects (images).  
The bitmap should be in the DOS path.
	
An image button will not support multi-line text.

If you change the display properties of the scroll bar of a simplelist and 
click OK, the changes are accepted.  Returning to the display dialog and 
selecting CANCEL will revert to the original display.
	
The Snap feature in the Form Preferences Dialog does not take effect 
until Show is selected.
	
Grid Size 32 is not displayed on the monitor.  Objects can be snapped to 
the grid.
	
F5 (Clear Form), F6 (Clear Field) and Form.ClearSelectedField will not 
clear RadioBoxes, Simplelists, Dropdownlists and CheckBoxes.
	
An editbox that has been deleted and recreated will not be accessible in 
form test mode until the form is saved.
	
The fill selection "None" will not be applied to field projections.
	
Setting form preferences to show Dataframe Control and then 
deselecting  Show Dataframe Control Outlines causes the simple list box 
to paint incorrectly in design mode.  The simple list box will paint 
correctly in runtime operation.
	
Creating new or modifying an existing layout through the transaction 
builder deletes all non-data-connected fields.
	
Spacing between records specified in the layout dialog will not affect the 
records when running or printing the form 

If you create a form over an existing entity and then change the layout to 
be "custom" with the title displayed, the title will paint incorrectly.
	
Entering a Command Line in the OLE package dialog does not 
automatically apply the default icon.

Combo list controls display column delimiters (i.e. "|")

Group By based on a VarChar attribute does not work for browse form 
with LargeText.

In form test mode, an edit box derived from drop down list boxes will 
bleed through the drop down list box if the two overlap.  The edit box 
and drop down list box paint correctly at run time.
	
The display dialog for a newly placed checkbox will have its Box line 
set to none.  The control will draw a checkbox at run time.
	
"Same size" edit command will not make buttons the same size if the 
buttons have a different number of lines of text.
	
A form maximized in design time will remain maximized in test mode. 

Sorting can not be used on the master level of a group-by based form.

Tab key navigation is not supported in QBF (Query By Form) mode.
	

=======================================
DATA ENTRY	
=======================================
	
To modify a  new record use F8 (save changes).  To create a new record 
use F2 (save as new) Attempting to save a change to a record that 
violates a table constraint, then modifying the record (to not violate the 
table constraint) and attempting to save changes to that record again will 
overwrite the original record. 
	
Entering the maximum values for Int and Smallint datatypes displays a 
blank field.
	
When browsing through a set of records, if one record is modified, and 
then the user continues to scroll, Enterprise Developer will inform the 
user that there are no more records.
	
Group By is not applied to forms when the form receives data for a new 
record from the list view

Interlaced GIF files cannot be used to populate an ImageField.
	
Enterprise Developer will only store the first 14 digits of a float field 
although up to 19 digits may be entered.
	
Non-data connected fields are not projected for record entry in a list 
view.
	
Selection criteria specified for data by the application developer can be 
over ridden by the user in run time data retrieval.
	
Revert (Ctrl-F5) from the Menu does not re-display the value of 
LargeBinary field cleared by using F6.
	

=======================================
STYLES
=======================================	
Chart objects and OLE objects do not inherit definition information from 
a style form.

Data frames created from the transaction builder do not inherit styles 
until the dataframe layout is changed. 
	
Record objects inherit from control styles and not from a pre-placed 
record object on a form style.
	
"Size window to form" check box on the Form Window Properties 
Dialog does not inherit from a style to a previously "unstyled" form.

	
=======================================
SCALESCRIPT	
=======================================

In the charting object.GetColumnData method with a FOR loop nested 
inside an IF statement, the END for the FOR loop ends the IF statement 
and jump out of the script in debugger mode.
	
The zoom ratio cannot be changed from the debugger.
	
App.InsertRecord() will not insert a largebinary field or VARtext.
	
The selection criteria in an ebEntity 'Open" statement will not accept a 
VARtext variable.
	
The string  "IntoView" should not be used as part of a column or table 
name in an Exec SQL statement.
	
Stored procedures created with OUT and IN OUT parameters will not 
return values to Enterprise Developer. 
	
A picklist on a data-connected form cannot be populated  from a 
superstring if the choices are longer than the field definition.  The 
choices will not be redrawn correctly and will stay highlighted even 
when another selection has been chosen.
	
Fields and objects named with a SCALEScript reserved word cannot be 
referenced  in a script/method
	
The Value property of a Checkbox object is always returned as zero, 
whether the object is checked or not checked. 

To have the Value property of a Choice object return a "yes" or "no" in 
agreement with its value, assign the Value to a text variable. A number 
variable will always be return zero, "0".

Use app.public variables instead of global superstring to add values in a 
script.
	
To " Extern:" more than one global variable per object  use  App.public 
variables for additional variables.
	
Direct expressions can not be used in conditional statements.
	
The MouseExit event will continuously fire until the next mouse event 
when an object is exited with the mouse down.
	
App.FindOpenForm always returns NULL for Childwindows.

"Break" can not be used to exit a CASE statement.

EXEC SQL doesn't recognize the difference between NULL and 0.
	
EXEC SQL script to create a table can not be executed from a non-data 
connected form.

SCALEScript does not support global definition of structures or 
structures within structures.
	
Form.OpenRelatedChild will not create a window when a NULL is 
passed in for the WindowHandle. 

Form.Help will not display. 
	
#include "filename.h" only works for files in the repository directory.
	
The form.formview method should not be used on a non-data-connected 
form.
	
To assign a NULL value to a complex variable, such as an ebControl, 
typecast the variable.
	
To assign the value of a text variable to a field name use .value after the 
field name.
	
There is a 12 level limit for recursive procedures.
	
The UpdateRecords method can not be used with direct assignment 
statements.
	
The "For...downto" command will not automatically decrement.
	
DateName: applies to HH will only return a 24-hour style answer.
	
Using App.InsertRecord can not be used to insert directly into a 
LargeText fields.

The PasteValue Method will not fire for certain edit box objects.
	
Record.Copy and Record.Paste do not work.
	
The value property for a Boolean object cannot be set , it remains 0.
	
ComboBox.EditBox.Value = null can not be accessed from a script.
	
Border.WidthY will compile in a script but will not have an effect.
	
Object names & menu script names should not be the same.

ValueRequired returns "0" when 'required' is set for an object.
	
The BringToFront() property is not working for list controls, standard 
buttons, and form variables.
	
Rect.(top, left, right, bottom) will not resize an on screen OLE.

Use ListShow() to activate a Scroll bar on a manually populated list

DropDownCombo.EditBox.Border.WidthX cannot be modified.
	
Changing the active page of a form does not refresh the object list tree 
when the script editor is open.

The DblClicked event will not fire for editbox controls, combobox 
controls, or imagefields.
	
The "Replace and Find" function in the script editor must be reset for 
each new script.
	
Trailing spaces after a method in App::NewMethods creates compile 
errors for the line before the END statement.
	
Changing the value of timer count -1 (the value of an inactive timer) 
with the debugger begins a negative counting sequence.
	
Object.Show() should be used instead of Object.Draw() to repaint 
objects through a timer.

The value returned for length for a VARtext field is always one, "1"

The Spellmonth function only works for a full date value.


=======================================
REPORTS
=======================================

In the list view of a browse report, embedded subforms use the default 
number of rows across and down.
	
The scroll bar, in a Browse Mode report with output to the screen bigger 
than the screen workspace area, advances the form to the next record.  
	

=======================================
PRINTING
=======================================

Dataframe layout formatting options do not print in form builder mode.

Printing a Form snapshot during runtime in a Browse Report with a 
multiple record layout will only print the record on the first row.
	
Current Record and Form snapshot  are not supported from the print 
options dialog at  runtime.
	
The bottom and right sides editboxes with MS Gray shading  print as 
white from form builder mode. 

When print to window defaults is changed to Printer or File, it grays the 
current records.
	
Header and Footer borders only print the top  and left sides.    
	
Paper size resets to default when you enter the print setup dialog box.

Dropdown combo boxes are defined, and displayed, as Editboxes in 
Browse reports.
	
A report form with only a group by field and a virtual field with a 
lookup will not display data.
	
Printing a report to a file, without showing the settings dialog, will 
overwrite existing files, without prompting the user.


=======================================
CHARTS	
=======================================
	
Charts placed in a header or footer will not print in run mode in run 
mode.
	
When running a Horizontal Stacked bar chart in normal 3D, the Y axis 
values become reversed.
	

=======================================
MISCELLANEOUS
=======================================
External functions must exist in the DOS search path.
	

