I'm still having problems printing a form. We've created a form to print the same data that is in a window. The user is supposed to select the menu option to print the current record (or QBF List) - and it should print. However, we keep (more often than not) getting a windows error, which claims to be in PE.DLL.

In the program I use the following code:

    ORIG=SET_PROPERTY('SYSTEM','BLOCK_EVENTS',1)

    Call Utility('RUNWIN',PCommand)

    BACK=SET_PROPERTY('SYSTEM','BLOCK_EVENTS',ORIG)

PCommand evaluates to REPORTER.EXE with a number of switches. I 'thought' I had this working yesterday, because I tried it numerous times and it worked fine. Today (when the users tried it) it is getting the PE.DLL error again - as do I.

Has anyone done something like this? How?

After doing an upgrade to 3.6 - should the client install be run again, or is there a new client install for 3.6? (just fishing for possibilities here.)

Thanks for any help,

Jeff

Hi Jeff,

A few questions come to mind.

1) What exactly does pCommand hold?

2) Why do you need to set 'BLOCKEVENTS'?

3) How are you passing the keys to reporter?

 Did you look at this [url=http://www.revelation.com/WEBSITE/knowledge.nsf/88e0581886ff6a0d8525651c004caecf/bb2ba418864d3302852565370049a963?OpenDocument]article[/url] on printing single or multiple records in reporter?

4) What is the configuration of your PC?

You do not have to do the client install again for 3.6.

Please let me know this information when you get a chance.

Thanks…

Blaise

A few questions come to mind. 1) What exactly does pCommand hold?

PCommand=.\REPORTER.EXE /AP=GLENN/UN=PRINTUSER/RP=CONTACT_INFO.RPT/REP=1/PR=1/BA=1/QU=1

2) Why do you need to set 'BLOCKEVENTS'?

Originally I wasn't using that - I saw it in an example and it didn't seem to hurt - just trying it.

3) How are you passing the keys to reporter?

Using the GETLIST KEY_PRINT@STATION method - which is working fine.

Did you look at this article on printing single or multiple records in reporter?

Yes

4) What is the configuration of your PC?

All the PC's in question are running Win95, Netware Client 32 (or the newer Netware Client). 32meg memory. The application is running off a network drive. We deploy to a runtime environment - but I'm getting the error messages both in development and runtime. I've tried copying the 3.6 reporter.exe to the runtime environment to see if it behaved better, and I 'thought' it did - but now it's not. Reporter.run doesn't look like it has changed in awhile.

Any ideas?

Jeff

Jeff,

A few things to try:

1) In PCommand, use spaces to separate the parameters.

2) Try running the report using the 'REPOSITORY' command instead of the 'UTILITY' command.

3) What happens if you take out the 'BLOCKEVENTS'?

Let me know what happens…

Blaise

PCommand=.\REPORTER.EXE /AP=GLENN/UN=PRINTUSER/RP=CONTACT_INFO.RPT/REP=1/PR=1/BA=1/QU=1

1. Change /REP to /RE

2. Put spaces between parameters (I don't know if it is necessary but it looks odd without them).

Cameron Purdy

[email protected]

1. Change /REP to /RE 2. Put spaces between parameters (I don't know if it is necessary but it looks odd without them). 1.) I've used both /REP and /RE - no difference in performance. There is a discrepancy between the help documentation (/REP) and the hard copy reference we have (/RE) - however, they both seem to work. 2.) I've tried this with and without spaces - the only space that seems necessary is the one right after reporter.exe. The rest are ok either way. I've also tried both the 'repository' command and the 'utility' command - I can get it to work 'sometimes', and other times I end with a windows error - which ultimately says it is in PE.DLL. Once we get the error, nothing short of a reboot will allow it to work again. Then it may work once or twice, I get the error, I reboot, it works once or twice, I get the error, . . . I would feel better if just worked or didn't work - this 'sometimes' stuff can drive you crazy. </QUOTE> —- === At 16 APR 1998 03:55PM Cameron Revelation wrote: === <QUOTE>Jeff, I've also tried both the 'repository' command and the 'utility' command - I can get it to work 'sometimes', and other times I end with a windows error - which ultimately says it is in PE.DLL. What is the exact text of the PE.DLL error message when executed in OI 3.6? Cameron Purdy [email protected] </QUOTE> —- === At 16 APR 1998 04:25PM Jeff Blinn wrote: === <QUOTE>What is the exact text of the PE.DLL error message when executed in OI 3.6? FWIW, when I just tried this again, the development copy was working ok - runtime blew up. All goes well until the Printing page 1 of whatever dialog box comes up. Then a white box appears with: Reporter An error has occurred in your program. To keep working anyway, click Ignore and save your work in a new file. To quit this program, click Close. You will loose information you entered since your last save. If I click 'Close', I get: Reporter This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor. The 'Details' button shows: REPORTER caused a general protection fault in module PE.DLL at 0001:000025be. Registers: EAX=c0012c5f CS=5cbf EIP=000025be EFLGS=00000286 EBX=012f076e SS=5b6f ESP=0000cb5a EBP=0000cb5c ECX=00000283 DS=2c5f ESI=815c10b8 FS=44cf EDX=815c0000 ES=44bf EDI=000002c0 GS=0000 Bytes at CS:EIP: c4 5e 06 26 8b 47 fe 24 fe 83 ed 02 8b e5 1f 5d Stack dump: cb7b2c5f 5fa70094 694702c0 010010b8 01010000 14d7815c 04a8cb8b 0000034f 0e8acb94 02c05fa7 00246947 24fc0000 414e18f7 000039bf cbae0100 5fa70868 </QUOTE> View this thread on the forum...