AXIANT

[Linnett, Richard]

If I could add my own personal view on the portability of code between
an Axiant mobile application and PowerHouse on the HP. 

First it depends a lot on what you are doing:

If you are writing a new application that you expect to run on both MPE
and in a mobile environment, then by working with a common subset of the
language, you should be able to write PowerHouse programs that work in
both environments.
  
- I'm not saying the code will be efficient - if you are using a
relational database, there is a lot you can and should do to take
advantage of the database. There is a definite balance between
portability and performance. 

- The same restrictions will apply on the server. The code and database
design will need to be a balance between portability and server
performance/functionality. 

- Have you considered using KSAM rather than Image for any portable
application subset? It would remove Image functionality from the
equation and a number of PowerHouse customers have managed to port
indexed applications to relational with few changes. 


If you are looking at migrating an existing PowerHouse / TurboImage
application to a mobile environment, there are many issues that will
probably need to be addressed.  For example:
 
- most Image databases are not fully normalized.  You must either modify
the Image database to bring it in line with the structures allowed by a
relational database, or accept that there will be a lot of code that is
different between application versions.  
- If the screen design in the application is very busy and really uses
all 24x80 screen positions, it will be a problem to fit those screens
into a workable windows environment