Release Notes for InfoMaker[TM] Version 5.0.02

© 1991-1996 Sybase, Inc. and its subsidiaries.  All rights reserved.

Updated 11/7/96


General Information
-----------------------

To Begin Installation

To install InfoMaker 5.0, please run SETUP.EXE from this CD 
and select the version of the software you wish to install
on your workstation.  NOTE:  Do not run setup16.exe 
or setup32.exe; these are two subroutines called by 
setup.exe.

During the setup process:
- If you press the escape key once setup has begun to install
  files, you will be notified of your intent to cancel as soon
  as the current file has finished copying.


'Autoconnect'  Enhancement to InfoMaker
------------------------------------------
A new database preference has been added to InfoMaker.   The new 
preference is "Connect DB at Startup".  It controls whether the 
connection is made to the database at startup or when appropriate 
painters are opened.  The traditional InfoMaker behavior of connecting 
at startup will be the default.  This new feature applies only to 
the development environment (not deployed apps).

The user preference is stored in IM.INI in the [pb] section and must 
be manually edited in this release of InfoMaker. A future release of 
InfoMaker will provide an interface in the InfoMaker development 
environment to enable and disable autoconnect.  The new entry is 
"autoconnect='n'", where 'n' may be 0 or 1. If no autoconnect entry 
exists, a value of '1' will be assumed and the database will be 
connected at startup as usual.

When autoconnect is set to zero,  InfoMaker does not attempt to connect 
to a database at startup.  Instead, it waits until one of the following 
painters is opened:   Form painter, Report painter, Query painter, Data 
Pipeline painter, Database painter, or Table painter.

NOTE to 16-bit InfoMaker Users:
The 16bit versions of PBSYS050.DLL and PBFRM050.DLL that contain the
autoconnect fix are located in a zip file, IMDEMO16.zip, on the Powersoft 
ftp site.

There is a known problem with this new feature on 16bit systems when 
entering the Form Painter.  16bit users who use autoconnect=0 must enter 
a painter other than the Form painter first (to connect to the database) 
before entering the Form painter. If you do not enter another painter first,  
you will experience db transaction errors previewing an existing form or 
a GPF creating a new one. This problem will be corrected in a future 
maintenance release of InfoMaker.


Troublshooting tips when attempting to use help from the preview painter.
---------------------------------------------------------------------------
On some Windows 16 systems, windows help is  unable to locate the help file 
IMHLP050.HLP from the Data Window preview painter.  This results in the error 
"unable to open help file".  to alleviate this problem, COPY IMHLP050.HLP from 
c:\pwrs\IM5\sys to c:\pwrs\sys.  


Troubleshooting Tips for Database Connections
--------------------------------------------- 
Follow these directions if you get IM003 or IM004 errors 
connecting to a database (including starting up InfoMaker for 
the first time).

These errors occur for a variety of reasons, but the basic cause 
is that the database engine components are not found by the 
application.  To fix, in Windows 3.x and Windows 95, you can add 
the database engine directory to your DOS path (for example, 
C:\SQLANY50\WIN32).

In Windows95, you can add it to the Registry AppPath for the 
executable.  For example, to add to the AppPath for InfoMaker 
(IM050.exe), look for the following entry in the Registry: 
HKEY_LOCAL_MACHINE/ SOFTWARE/Microsoft/Windows/Current Version/App Paths
/IM050.exe

Double-click on Path icon and add a semi-colon and the fully 
qualified path to the entry.

On NT, use Control Panel/System to edit your system path to add the 
appropriate pathing information.

The SQLANY environment variable (if exists) must point to the proper 
SQLANY50 directory (e.g. "C:\SQLANY50").  

On Windows or Winows 95, this is set in Autoexec.bat.

On NT,use Control panel/system to edit this variable.


Installing InfoMaker on a Network drive
-----------------------------------------
32-bit only:
If you have installed InfoMaker on a network, each client machine
that will be using IM will need to make some local Registry in order
to run machine. To make these entries, locate the Support\netinst 
directory and run Setup on each client machine.

This will run the IM Local Setup for Network Install, and create
the entries you need.   Run the setup as normal.  
When the products screen appears, modify the paths to the network 
drive and directories where the following components of Powersoft 
products *WERE* installed:

1) Path to Network IM shared - This is the path to the Powersoft 
   DLLs (or Shared Files).   
	WinNT default: pwrs\sys32
	Win95 default: Program Files\Common Files\Powersoft Shared

2) Path to Network IM - This is the path to IM050.EXE.  
	WinNT default: pwrs\pb5i32
	Win95 default: Program Files\Powersoft\InfoMaker 5.0 

3) Path to Network SQLAnywhere - This is the path to the SQLAnywhere 
   files.   If SQLAnywhere was not installed on the network, uncheck 
   this component.
   The default on both WinNT and Win95 is sqlany50\win32.

4) Path to Powersoft Demo Database - This is the path to the Demo 
   Database used on initial InfoMaker startup.
	WinNT default: pwrs\Im5i32\
	Win95 default: Program Files\Powersoft\PowerBuilder 5.0\

Continue with the install normally.  When the install finishes, you 
should have a program item for PowerBuilder, SQLAnywhere, the Demo 
Database and Uninstall on the local machine.

Latest Sybase SQLAnywhere release
---------------------------------

This CD contains release 5.02 of Sybase SQLAnywhere.


Running InfoMaker Applications
---------------------------------
When you build InfoMaker applications (executables) on Windows 95, 
you will need to register them in the Windows Registry and set up an 
APP PATH for them, so that the executable can find the Powersoft DLLs 
and any database files that it needs.  

Setup and CTL3D32.DLL
---------------------
On Win95 and WinNT, you may receive a message that there is an invalid 
version of ctl3d32.dll on your system.  You can press OK, and Setup 
will run normally; however the colors may be splotched, and the UI may 
not look as intended.

This happens because there are different versions of Ctl3d32.dll for 
Windows95 and WindowsNT.   Setup tries to install the correct version 
on your system, but this may fail if an invalid version was installed 
by another application.

To solve, exit setup.  Search your system for ctl3d32.dll, and rename 
any other instances to ctl3d32.old.  Upon running Setup again, Setup 
will install the correct version and run normally.

Editing SQL in a DataWindow, Pipeline or Query Object
------------------------------------------------------
If you are in graphical mode and choose to edit the SQL, hitting the 
SQL icon on the toolbar will get you there.  When you are in SQL edit 
mode, the SQL icon becomes depressed and cross-hatched and indicating 
that it is toggled to SQL mode.  Hit the SQL icon again to return to 
graphical mode.

HScroll in InfoMaker
--------------------
When scrollbars are defined for the report they appear ok at run time 
but only the vertical one appears in the design workspace.  This only 
happens in 32-bit WIN95, it is okay on other platforms.

Embedding PSRs in OLE container documents
-----------------------------------------
In order for this feature to work correctly (required for Windows 95 
logo certification), we had to implement the following:

InfoMaker is the server application for PSR files.  All files which 
InfoMaker needs to run need to be in the autoexec.bat path (or the 
oleclient path which is not feasible).  This includes database files, 
and Powersoft system dlls.

i.e.  path=c:\"program files"\"common files"\powersoft;
      c:\sqlany50\win32;%path%

The solution we implemented is to update the autoexec.bat path for 
32-bit apps on Windows 95 ONLY when InfoMaker is installed.  This may 
make your path quite long, especially if you are using the Long File 
Name install option.  There is no effect on NT, which uses the system 
path rather than autoexec.bat.

Change to ODBC Configurator
---------------------------

Microsoft's ODBC Configuration Tool no longer allows the use of 
parentheses in the Datasource name.

If you need to connect to a database that has parentheses in the name 
(such as Powersoft Demo DB (V4)), you will need to make changes 
directly in ODBC.INI to remove them.  This also affects any DBParms 
you have set for existing datasources either in Database Profiles or 
existing application ini files.

PowerWeb
--------
All installs are adding an icon called PowerWeb.  This is a small HTML
file which lets you link to the Powersoft Web site.  If you do not
have a web browser installed on your system, this entry will display 
a blank icon.


Suppressing Built-in Styles
--------------------------

In InfoMaker 4.0, you can suppress the display of built-in 
styles by adding a line to the [Window] section of the shared ini 
file:  ShowStandardStyles=0.  This suppresses the built-in styles and 
only shows styles which the developer has made available through the 
style library. There is no UI for this in IM5, nor does it even work 
if you place this entry directly into the shared IM.ini.

Using PBSYT050.DLL under Windows 95 
-----------------------------------

In order to use PBSYT050.DLL (Sybase DBLIB interface )under 
Windows95, you must update your OpenClient software with 
EBF # 6282 from Sybase.

Silent Install
--------------
The InfoMaker install allows you to create a setup file that can
be used to run multiple identical installs.  To see how to use this
feature, see the "InfoMaker Installation Guide".

Online Books Install
--------------------

The install for the Online Books will give you the choice of Typical,
Compact and Custom installs, but there is only one small viewer 
loaded, and no difference between what is installed under the 3 
options.


*****************************************************************
Known Anomalies in InfoMaker 5.0 FIXED in 5.0.01

(FOR A COMPLETE LIST OF FIXES, SEE THE TECH BULLETIN)

FIXED - OCXs in DataWindows
---------------------------
Previous problem description:
If you have an OCX as a container in a DataWindow, do not place it 
into the band layer. OCXs are always active, and creating multiple 
instances hangs the retrieve.  It is okay to place OLE servers into 
the band layer.

SOLUTION: The UI now will not allow OCXs to be placed in the band - 
the "band" value is not in the dropdown anymore if the container is
an OCX.

FIXED - Workstation Hang in Table Painter Syntax
------------------------------------------------
Previous problem description:
WIN3.1 only.  Table Painter Syntax View causes some workstations to hang.  
Requires reboot.  This was a problem using full compiler optimization in 
MSVC 1.52 under Win16.  

Solution:	Problem with executable code optimization in function 
TBL_DoSyntaxView( ) has been fixed.

FIXED - Renaming Tables using PBSYC
-----------------------------------
Previous problem description:
Trying to rename a table while connected to System10 with PBSYC from 
the Alter Table dialog causes InfoMaker session to hang. 

Solution:  Problem with executable code optimization in function
TBL_DoSyntaxView( ) has been fixed.


Known Anomalies in InfoMaker 5.0
--------------------------------

Cross-hatching in 3D graphs
---------------------------
3D Pie Chart reports when printed prints the same cross-hatch style  
for the different categories and is not distinguishable.   On printed 
page, two different categories print in the same crosshatch;  although 
each slice of the pie is printed in a different pattern.  There's no 
way to tell which slice of the pie belongs to which category.


DB/2 Primary Index Problem
--------------------------
On a Windows for Workgroups client attached to DB2/MVS through PBIBM, 
exporting the syntax of a (primary) index to the log file crashes 
InfoMaker with a non-specific Application Error.  In the error 
message, there is some garbled text. 

In the Database Painter with a table opened, click on a primary key 
and then select menu option \Object\Export to Log.  Should see the 
error message at this point.

Select Tables with Long filenames
---------------------------------
'Select Tables' dialog doesn't support horizontal scrollbar for 
long table names.

Horizontal scrolling for DropDownPictureListBoxes on 16-bit 
-----------------------------------------------------------

DropDownPictureListBoxes don't support hscroll.
 
The option is there, but nothing happens when you choose hscrollbar on 
a DropDownPictureListBox.

16-bit windows does not support CB_SETHORIZONTALEXTENT  which is 
required for proper operation of the horizontal scroll bar.  Because 
this is available for 32-bit, this was not removed.

*********************************************************************

© 1991-1996 Sybase, Inc. and its subsidiaries.  All rights reserved.
Sybase, Inc. and its subsidiaries ("Sybase") claim copyright in this 
Program and documentation as an unpublished work, versions of which 
were first licensed on the date indicated in the foregoing notice.  
Claim of copyright does not imply waiver of Sybase's other rights.  
See Notice of Proprietary Rights.

NOTICE OF PROPRIETARY RIGHTS

This computer program and documentation are confidential trade secrets 
and the property of Sybase, Inc. and its subsidiaries.  Use, 
examination, reproduction, copying, disassembly, decompilation, 
transfer and/r disclosure to others, in whole or in part, are 
strictly prohibited except the express prior written consent of 
Sybase, Inc. and its subsidiaries.



