Re: Problem in converting 1.1 reports to 2.0.13 : It's a BUG

In article <1994May3.180012.8857_at_synseer.Syntex.COM>, <Dilip.Pitkar_at_Syntex.Com> writes:
> Newsgroups: comp.databases.oracle
> Path: synseer!usenet
> From: Dilip.Pitkar_at_Syntex.Com
> Subject: Problem in converting 1.1 reports to 2.0.13
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Message-ID: <1994May3.180012.8857_at_synseer.Syntex.COM>
> Sender: usenet_at_synseer.Syntex.COM
> Nntp-Posting-Host: pdkpa3.syntex.com
> Organization: Syntex U.S.A. - Palo Alto
> Hi Friends,
>
> Have any of you faced this or similar problem? could somebody
> enlighten me on this?
>
> My problem is as follows:
> -------------------------
>
> I tried to convert SQL*REPORTWRITER 1.1 reports to 2.0 using 'oracle reports
> 2.0 move' utility. It gave the error:
>
> REP-0203: Passed a null pointer as a handle
> (Definition Manager Memory Subsystem)
>
> When I clicked on <OK> button, it further said:
>
> R20MREP General Protection Fault
> R20MREP.EXE at 0005:411C.
>
>
> Some background:
>
> ORACLE: 7.0.14
>
> REPORTWRITER: 2.0.13 installed on a PC-Client, talking to a VAX-based server
 

> using SQL*NET-NETMANAGE 2.11 , TCP/IP - No problems is connecting
> to database or developing a new report on 2.0
>
>
> Thanx & Regards,
>

May I add little to the above:

1. I reported this to oracle tech support group.
2. After half an hour, I got a reply that YES, It is a bug. Also, a way to go around was also suggested as follows:

   This happens where DESNAME (A parameter Destination file/printer name)    is used somewhere in text. (I was printing the DESNAME parameter on 1st    page of report.) Remove this parameter from the text and it works fine.

3. Thanx to all those who responded. (Especially, to Keith Majkut, who very

   well guessed what the problem can be. The tar # : 105349.198) Received on Thu May 05 1994 - 17:34:05 CEST