Is anyone having success with running a CR 10 report with Rep32? I am
having random crashes with the Oleautoclient method and I am looking to
switch to using the API method instead. The PEOutputToWindow() function
returns False. Any comments?

Thanks,
Ken

From:	mimcl
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Wed, 29 Dec 2004 17:38:37 -0500

I'm running in to the same problem. My workaround for now is to run the
report as a separate executable. The report is only run once and the
report executable exits. This reduces the possibility of a crash.

The environment I’m using is Windows 2003 Terminal Server, dBase Plus
2.5, and Crystal 10.

What is the API method?

MM
Ken B wrote:
> Is anyone having success with running a CR 10 report with Rep32? I am
> having random crashes with the Oleautoclient method and I am looking to
> switch to using the API method instead. The PEOutputToWindow() function
> returns False. Any comments?
>
> Thanks,
> Ken
>
>

From:	Ken B
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Thu, 30 Dec 2004 09:20:41 -0500

> I'm running in to the same problem. My workaround for now is to run the
> report as a separate executable. The report is only run once and the
> report executable exits. This reduces the possibility of a crash.
Maybe I could do something similar.

>
> The environment I’m using is Windows 2003 Terminal Server, dBase Plus 2.5,
> and Crystal 10.
I have customers using Win 2000 TS & Win 2003 TS, dBase Plus 2.01 and CR 10.
>
> What is the API method?
The API method is using function calls into the crpe32.dll. Crystal has
discontinued support for it so some of the new features in CR v10 are not
supported at all. You can download the rep32.prg from the dbasetalk.com
codelib newsgroup. Search for rep32.prg by Jim Sare on 11/4/2004.

Thanks,
Ken

From:	news.alldbase.com
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Thu, 30 Dec 2004 10:09:23 -0500

I also use this method. I run a separate EXE with the Crystal Reports. I
pass parameters via command line and INI file. I use Jim Snare's runWait.prg
to halt program execution until the report EXE completes.
Also get rid of any sub-reports you are using also if possible, as they seem
to slow display of the reports greatly and may be causing a memory leak.
Reports with a lot of sub-reports seem to crash more often.
I also use the Crystal merge modules to install the Crystal runtime on
customer machines which seems to have stabilized Crystal even more.

--
Rich...
www.autotraker.com
AutoTraker Inc.

"mimcl" wrote in message
news:cwN3vff7EHA.1844@news-server...
> I'm running in to the same problem. My workaround for now is to run the
> report as a separate executable. The report is only run once and the
> report executable exits. This reduces the possibility of a crash.
>
> The environment I’m using is Windows 2003 Terminal Server, dBase Plus 2.5,
> and Crystal 10.
>
> What is the API method?
>
> MM
> Ken B wrote:
>> Is anyone having success with running a CR 10 report with Rep32? I am
>> having random crashes with the Oleautoclient method and I am looking to
>> switch to using the API method instead. The PEOutputToWindow() function
>> returns False. Any comments?
>>
>> Thanks,
>> Ken
>>

From:	Ken B
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Wed, 5 Jan 2005 11:00:20 -0500

>I also use this method. I run a separate EXE with the Crystal Reports. I
>pass parameters via command line and INI file. I use Jim Snare's
>runWait.prg to halt program execution until the report EXE completes.
> Also get rid of any sub-reports you are using also if possible, as they
> seem to slow display of the reports greatly and may be causing a memory
> leak. Reports with a lot of sub-reports seem to crash more often.
> I also use the Crystal merge modules to install the Crystal runtime on
> customer machines which seems to have stabilized Crystal even more.
----
Hi Rich,

Why do you use this method and why do you use the RunWait.prg? It seems
rather limiting to only have one report displayed at once.

I don't use any subreports, they are usually based on a flat file that is
loaded prior to calling the report. I also use the merge modules for
installation.

Do you know of any problems with having Charts in a report?

Thanks,
Ken

From:	news.alldbase.com
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Thu, 6 Jan 2005 13:55:14 -0500

Most the time we want to stop program execution during a report because
quite a few of our users will have 500 reports on the screen without even
knowing it. Also less problem with temp files we create and delete on the
fly. If I had enough customers looking for the abilities to open multiple
reports simultaneously, I'll looking into doing it a different way. This
works for us and we have zero problems.
No problems with charts. They have some really nice looking ones.

--
Rich...
www.autotraker.com
AutoTraker Inc.

"Ken B" wrote in message
news:v0sntD08EHA.1088@news-server...
> >I also use this method. I run a separate EXE with the Crystal Reports. I
> >pass parameters via command line and INI file. I use Jim Snare's
> >runWait.prg to halt program execution until the report EXE completes.
>> Also get rid of any sub-reports you are using also if possible, as they
>> seem to slow display of the reports greatly and may be causing a memory
>> leak. Reports with a lot of sub-reports seem to crash more often.
>> I also use the Crystal merge modules to install the Crystal runtime on
>> customer machines which seems to have stabilized Crystal even more.
> ----
> Hi Rich,
>
> Why do you use this method and why do you use the RunWait.prg? It seems
> rather limiting to only have one report displayed at once.
>
> I don't use any subreports, they are usually based on a flat file that is
> loaded prior to calling the report. I also use the merge modules for
> installation.
>
> Do you know of any problems with having Charts in a report?
>
> Thanks,
> Ken
>

From:	Ken B
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Thu, 6 Jan 2005 15:47:21 -0500

> Most the time we want to stop program execution during a report because
> quite a few of our users will have 500 reports on the screen without even
> knowing it. Also less problem with temp files we create and delete on the
> fly. If I had enough customers looking for the abilities to open multiple
> reports simultaneously, I'll looking into doing it a different way. This
> works for us and we have zero problems.
> No problems with charts. They have some really nice looking ones.
---
Thanks for the reply Rich.

I tried using the RunWait.prg but it doesn't stop the program. How are you
calling your .exe?

Ken

From:	news.alldbase.com
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Fri, 7 Jan 2005 10:50:01 -0500

Strange how I sometimes forget what I have done.
I'm not actually using runwait.prg by Jim Sare. It was what I had remembered
that I was using. When I looked at the code to give you an example, I
discovered that I was using an altered version of Shellandwait.prg by Vic
McClung. So I guess my example is not going to work for you. I do however
use Jim's runwait.prg in other places, just not for reports. An example is
below. I run the runtime which then runs the dBASE exe. This speeds things
up considerably. These parameters for RunWait I think are the defaults, but
this is how it exists in my code because I do change things depending on
what I'm running.

set procedure to RunWait.prg additive
if "RUNTIME" $ upper(version(0))
Cmd= home()+"PLUSrun.exe "
else
Cmd= _dbwinhome+"runtime\"+"PLUSrun.exe "
endif
Cmd += "report.exe"
RunWait(Cmd,true,0xFFFFFFFF,set("directory"))

--
Rich...
www.autotraker.com
AutoTraker Inc.

"Ken B" wrote in message
news:kLw1yID9EHA.1176@news-server...
>> Most the time we want to stop program execution during a report because
>> quite a few of our users will have 500 reports on the screen without even
>> knowing it. Also less problem with temp files we create and delete on the
>> fly. If I had enough customers looking for the abilities to open multiple
>> reports simultaneously, I'll looking into doing it a different way. This
>> works for us and we have zero problems.
>> No problems with charts. They have some really nice looking ones.
> ---
> Thanks for the reply Rich.
>
> I tried using the RunWait.prg but it doesn't stop the program. How are
> you calling your .exe?
>
> Ken
>

From:	Ken B
Subject:	Re: Crystal Reports 10 and Rep32.prg
Date:	Fri, 7 Jan 2005 11:13:24 -0500

Thanks Rich