Axiant 2.03 - 3.0

[Whittall, Conrad]

Hello Bjorn,

I'm sure that others will contribute their experiences and recommendations
for upgrading from Axiant 2.03 to 3.0, but there is one particular feature
of the upgrade process that I strongly recommend that you use.

That feature is having the Axiant 3.0 repository upgrade process
automatically add Event and Toolbar sections to all of your existing screen
programs. See the section entitled "Upgrading Axiant 4GL 2.02 or 2.03
Repositories" in the Axiant 3.0 Windows Help, under "Axiant 4GL Release
Notes | Upgrade Information for Existing Axiant 4GL Users".

Doing this will mean that you can immediately benefit from the new default
point-and-click interface for fields in Axiant screen programs, and from the
new user toolbars. Even if your application currently uses hot area buttons
over data fields to simulate a point-and-click interface, I would recommend
that you have Axiant 3.0 automatically add the Event section that controls
this as you upgrade your existing repository. The processing triggered by
the new Event section will not take effect until you remove the hot area
that is positioned over the field, since the hot area is effectively masking
the field from the user and so when a user clicks over the field they are
clicking the hot area and not the field itself (where the Event section
would be triggered). You may then be able to use the find and change
capabilities within Axiant 3.0 to find and remove the hot areas (and simply
delete the corresponding procedures from the Procedure Section if they are
no longer needed).

Even if you don't plan on using the capabilities of the new Event and
Toolbar sections immediately it is far easier to have the Axiant 3.0 upgrade
process add the inheritance of these sections to your existing screen
programs than for you to go back and add them manually after converting your
repository to the 3.0 format. If you don't want to use the capabilities of
these sections straightaway you could simply delete the objects that appear
in the default sections that are being inherited (in the library in which
they exist) so that these sections are empty when inherited by the programs
at build time.

Best regards,
Conrad

Conrad Whittall
Marketing Manager, Application Development Tools
Cognos Incorporated, 3755 Riverside Drive, Ottawa, Ontario, K1G 4K9, Canada

Developer productivity never goes out of style!

For details of the Cognos PowerHouse family of high-productivity
development tools for Web, Windows and terminal-based business
applications, and to request your own free copy of our new product
demo CD, simply click here http://www.cognos.com/powerhouse.

-----Original Message-----
From: Bjorn.Selfors@kby.BERGEN-KOMMUNE.telemax.no
[mailto:Bjorn.Selfors@kby.BERGEN-KOMMUNE.telemax.no]
Sent: Wednesday 9 May 2001 09:16
To: powerh-l@lists.swau.edu
Subject: Axiant 2.03 - 3.0

We are planning to upgrade from Axiant 2.03 to 3.0 in a NT / Oracle
environment.
Anybody have any experience about this upgrade? What should we be aware of?

Bjorn Selfors
Delfi Data a.s.
Tlf +47 5556 8887 
http://www.delfidata.no