Skip to main content

[archive] Crystal Reports Problem using 7.2 runtime

  • September 28, 2006
  • 4 replies
  • 0 views

[Migrated content. Thread originally posted on 27 September 2006]

I am having a problem using the Crystal Reports engine (CRPE32.DLL) with
the 7.2 run time. A program that works just fine with the 5.2.1.1 runtime fails using 7.2. Most of the Calls to CRPE32.DLL work, but one of them return invalid values.

I have isolated this to the 7.2 run time.

The program compiled and executed with 5.2.1.1 code works fine considering everything else is equal (same db, same report etc).

If I compile and execute it with 7.2 it fails.

If I execute the 5.2.1.1 program with the 7.2 runtime it fails in the same manner.

The call that returns the invalid value is PEGetSectionCode.

I would appreciate hearing from anyone with a similar problem.

4 replies

[Migrated content. Thread originally posted on 27 September 2006]

I am having a problem using the Crystal Reports engine (CRPE32.DLL) with
the 7.2 run time. A program that works just fine with the 5.2.1.1 runtime fails using 7.2. Most of the Calls to CRPE32.DLL work, but one of them return invalid values.

I have isolated this to the 7.2 run time.

The program compiled and executed with 5.2.1.1 code works fine considering everything else is equal (same db, same report etc).

If I compile and execute it with 7.2 it fails.

If I execute the 5.2.1.1 program with the 7.2 runtime it fails in the same manner.

The call that returns the invalid value is PEGetSectionCode.

I would appreciate hearing from anyone with a similar problem.
I would report this to Acucorp technical support

[Migrated content. Thread originally posted on 27 September 2006]

I am having a problem using the Crystal Reports engine (CRPE32.DLL) with
the 7.2 run time. A program that works just fine with the 5.2.1.1 runtime fails using 7.2. Most of the Calls to CRPE32.DLL work, but one of them return invalid values.

I have isolated this to the 7.2 run time.

The program compiled and executed with 5.2.1.1 code works fine considering everything else is equal (same db, same report etc).

If I compile and execute it with 7.2 it fails.

If I execute the 5.2.1.1 program with the 7.2 runtime it fails in the same manner.

The call that returns the invalid value is PEGetSectionCode.

I would appreciate hearing from anyone with a similar problem.
I thought about that. What is stopping me is the difficulty in
providing an example program that illustrates the problem.

[Migrated content. Thread originally posted on 27 September 2006]

I am having a problem using the Crystal Reports engine (CRPE32.DLL) with
the 7.2 run time. A program that works just fine with the 5.2.1.1 runtime fails using 7.2. Most of the Calls to CRPE32.DLL work, but one of them return invalid values.

I have isolated this to the 7.2 run time.

The program compiled and executed with 5.2.1.1 code works fine considering everything else is equal (same db, same report etc).

If I compile and execute it with 7.2 it fails.

If I execute the 5.2.1.1 program with the 7.2 runtime it fails in the same manner.

The call that returns the invalid value is PEGetSectionCode.

I would appreciate hearing from anyone with a similar problem.
This problem was resolved by Acucorp Support.

Setting the configuration variable CALL_HASH_SIZE to "0"

Resolved the problem.

[Migrated content. Thread originally posted on 27 September 2006]

I am having a problem using the Crystal Reports engine (CRPE32.DLL) with
the 7.2 run time. A program that works just fine with the 5.2.1.1 runtime fails using 7.2. Most of the Calls to CRPE32.DLL work, but one of them return invalid values.

I have isolated this to the 7.2 run time.

The program compiled and executed with 5.2.1.1 code works fine considering everything else is equal (same db, same report etc).

If I compile and execute it with 7.2 it fails.

If I execute the 5.2.1.1 program with the 7.2 runtime it fails in the same manner.

The call that returns the invalid value is PEGetSectionCode.

I would appreciate hearing from anyone with a similar problem.
I seems like the CALL_HASH_SIZE config variable works as long as the
code was compiled with the 5.2 compiler (and run with the 7.2 runtime).

If it is compiled with the 7.2 compiler this workaround does not work.
Example sent to Acucorp support.