[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

Re: Unable to print SQR report direct from Maximo4 or SQRWB4



I ran into a similar problem when I upgraded to Maximo 3.02.
The solution that was passed on to me (from another user as PSDI
wsa NO help) was to craete an empty directory on my local hard
drive.  Then, right click on the shortcut icon that is used to
start maximo (be it in the start directory or just on the
desktop) and click on 'PROPERTIES' and go to the 'SHORTCUT' tab.
In there, delete whatever is in the 'START IN' line and replace
it with the path to the newly created empty directory.  Once I
did this, I was able to print directly.  The only painful part
of it is that it has to be done on all user systems to all
shortcuts that they use to run Maximo.

Hope this helps.

Jeremy Smith
jcsmith@cmu.edu


On Thu, 7 Jan 1999 11:13:55 +0000 Martin Hunter
<Martin.Hunter@THAMESWATER.CO.UK> wrote:

> Dear All,
>
> RE:  Unable to print direct from PSDI Maximo v4 or SQR WB v4.
>
> I am running PSDI Maximo v4 (NT Terminal Server) over an Oracle (Unix)
> database. Users access the server through Citrix Metaframe, over a Novell
> LAN.
>
> I am having difficulty getting a report that I have written to print
> directly (i.e. NOT via preview) from both the Maximo front-end and SQRWB. I
> can preview, and I can print from preview, but an address exception error
> occurs when I try to print direct. The printers I am trying to print to are
> on the Novell LAN.
>
> Dr Watson for NT has provided me with the associated machine code, which on
> close inspection reveals a div/0 error. This machine code belongs to
> SQRP.exe (SQR Print).
>
> SQRP.exe's error file logs the error '6602' - which is usually associated
> with resource problems.
>
> This print problem occurs only with one report - all others (some 20+)
> print directly, and preview, perfectly from both Maximo and SQRWB. These
> reports include both ones written by PSDI for Maximo, and ones written by
> myself.
>
> There are two avenues that I have so far pursued:
>
> (1) Memory inadequate.
>
> At first glance the machine code and SQRP.exe errors pointed me towards a
> lack of memory. However, the server machine has 750MB RAM - so I thought it
> unlikely that this could be the problem. To be sure I have run the report
> (through both Maximo and SQRWB) with only skeleton processes and all users
> logged out. I have also given SQRP.exe real-time memory priority. The
> problem still occurs.
>
> (2) Compilation error.
>
> I thought it possible that the SQR compiler has turned out some rubbish on
> this occasion. To test this, I have compiled my report several times on
> three different NT Terminal Servers, and tried attaching each server to
> three separate Oracle databases. I have also re-written the report in a
> fresh SQR file in order to remove any possible blips in the SQR code. The
> problem persists.
>
> It seems strange also that the preview (SQRV.exe, SQR Viewer) CAN read the
> report without any problems, but SQR Print (SQRP.exe) should not be able to
> do the same. If it were a compilation error, could I expect both to fall
> over?
>
>
> I am assuming that I can print from SQRV.exe because it has it's own print
> routine, and does not call SQRP.exe.
>
>
> Any ideas?
>
>
> Cheers,
>
> Martin Hunter, SSIL.

----------------------
Jeremy Smith
jcsmith@cmu.edu
x86093