GPF / Forms Builder 6 Object List Report
From: Martin Angers <mangers_at_larochelle-gratton.com>
Date: Thu, 30 Dec 1999 11:45:44 -0500
Message-ID: <gX1b4.3271$to1.95946_at_weber.videotron.net>
We are using the Object List Report feature of Forms Builder 6.0.5 on Windows NT 4 to generate documentation of forms and menus and then we insert this information in a database (we built a tool that parses the text file to gather the information we want). It works fine for most of the over-200 forms of the application, but for some 35 of them, Forms Builder generates a GPF when we execute the Object List Report (formerly Forms Doc). I heard about a workaround saying to put the long TRIGGER code into a Program Unit, but for some of these forms, the GPF is caused by long Program Units code...
Date: Thu, 30 Dec 1999 11:45:44 -0500
Message-ID: <gX1b4.3271$to1.95946_at_weber.videotron.net>
We are using the Object List Report feature of Forms Builder 6.0.5 on Windows NT 4 to generate documentation of forms and menus and then we insert this information in a database (we built a tool that parses the text file to gather the information we want). It works fine for most of the over-200 forms of the application, but for some 35 of them, Forms Builder generates a GPF when we execute the Object List Report (formerly Forms Doc). I heard about a workaround saying to put the long TRIGGER code into a Program Unit, but for some of these forms, the GPF is caused by long Program Units code...
Is there a patch available or is there a workaround to this problem (other than moving the code to a program unit)?
Thanks,
-- Martin Angers Larochelle Gratton mangers_at_larochelle-gratton.comReceived on Thu Dec 30 1999 - 17:45:44 CET