Uniface Print function crashes Uniface application

Author: sdale@csc.com (sdale)

Hi

I have a problem reported by my customer that results in the Uniface application crashing when printing from one specific form.

This has only been reported against one form in an application that has been around under various versions of Uniface for 15 years, there are 300 active forms in this application. The form uses the Uniface "print" statement in the form print trigger which is activated from a menu option executing a macro "^print" command, resulting in the following statement being executed in the form print trigger:

print "DX00PRT092POR", "A"

 

Where DX00PRT092POR is the print job model - this has not changed during the life of the application and is shared by the majority of other forms.

The form has not changed for quite some time > 4 years. This problem may have always existed but it has never been reported before.

We have no idea what is causing the problem. Can any one point us to any possible cause for this and any solution?

Client version of Uniface is 8.4.05 running under Windows XP over TCP to a Solaris 10 app server running Uniface 8.4.05 and Oracle 10gr2 database.

Any help would be apprciated.

Thank you in advance

Stephen

7 Comments

  1. It's a print "A". Does it retrieve too much data?


    Author: Theo Neeskens (tneeskens@itblockz.nl)
  2. Hi

    Thanks for the quick response.

    I suspect not as I can attempt to print the full hit list or a single occurrence with the same result.

     

     


    Author: sdale (sdale@csc.com)
  3. Difficult to give more suggestions without more info. - When you run it in the debugger, on what statement does it crash? - Can you make a logfile with io level 255, and make a screenprint of the crash? - Do you have references to excluded fields? Try setting fieldlist to all fields. - Did the Uniface Model or the database change? Did you recompile the Report after that?


    Author: Theo Neeskens (tneeskens@itblockz.nl)
  4. Hi Stephen

    Are there 'area frames', 'line frames' (lines) and/or 'page breaks' painted?

    We got a crash in some cirumstance due to 'borders' around some page breaks.

    To find the exact error, just copy the form and remove all lines and 'area frames'. Recompile and try again to get the crash.

    If there is still a crash, remove the 'page breaks'

    If you did found the point of interest, try the rearrange the surface

     

    Regards Ingo

     

     


    Author: istiller (i2stiller@gmx.de)
  5. Hi

    Great advice. Thank you.

    I have managed to stop the crash by removing all area frames on the form and have subsequently isolated it to one area frame.This is the area frame that surrounds the main database entity of the form. What the form does is to display a list of records in the main body of the form but then presents a foreign entity providing more detail for the current occurrence selected in the main entity frame.

    The form is used primarily for the retrieval and presentation of data through the windows GUI and printing is an option that a few users use. To my knowledge there was no specific development for printing in the original form concept.

    I have not yet rebuilt the form but before I do is there any advice I should consider before adding back the area frames to prevent it happening. It is a very long time since I did any active development for form printing so references to page breaks does not ring any bells. I notice that the area frame has a number of printing attributes that I am not familiar with.

    Any further help would be appreciated.

    Thank you

    Stephen

     


    Author: sdale (sdale@csc.com)
  6. Hi

    Great advice. Thank you.

    I have managed to stop the crash by removing all area frames on the form and have subsequently isolated it to one area frame.This is the area frame that surrounds the main database entity of the form. What the form does is to display a list of records in the main body of the form but then presents a foreign entity providing more detail for the current occurrence selected in the main entity frame.

    The form is used primarily for the retrieval and presentation of data through the windows GUI and printing is an option that a few users use. To my knowledge there was no specific development for printing in the original form concept.

    I have not yet rebuilt the form but before I do is there any advice I should consider before adding back the area frames to prevent it happening. It is a very long time since I did any active development for form printing so references to page breaks does not ring any bells. I notice that the area frame has a number of printing attributes that I am not familiar with.

    Any further help would be appreciated.

    Thank you

    Stephen

     


    Author: sdale (sdale@csc.com)
  7. Hi

    Great advice. Thank you.

    I have managed to stop the crash by removing all area frames on the form and have subsequently isolated it to one area frame.This is the area frame that surrounds the main database entity of the form. What the form does is to display a list of records in the main body of the form but then presents a foreign entity providing more detail for the current occurrence selected in the main entity frame.

    The form is used primarily for the retrieval and presentation of data through the windows GUI and printing is an option that a few users use. To my knowledge there was no specific development for printing in the original form concept.

    I have not yet rebuilt the form but before I do is there any advice I should consider before adding back the area frames to prevent it happening. It is a very long time since I did any active development for form printing so references to page breaks does not ring any bells. I notice that the area frame has a number of printing attributes that I am not familiar with.

    Any further help would be appreciated.

    Thank you

    Stephen

     


    Author: sdale (sdale@csc.com)