Jump to content


Steve Kiernan

Member Since 30 Jun 2000
Offline Last Active Sep 11 2012 11:48 AM
-----

Topics I've Started

function exceeds workspace

06 September 2012 - 11:10 AM

Hi,

We're using 5.5 Windows version and are having problems with a function.

It's a report and is quite large with 62 characteristics and various files, logics etc.

We frequently experience "function exceeds workspace" when running it.

The metrics as it currently stands are:
Logics:38006
Global Logics: 6598
Formats: 2
Fields: 4284
Base: 0
Symbol Table: 80104

Over the years we've tried, on a trial and error basis, several things - reducing the number of file variables with alternate definitions, defining all scratch vars, reducing the number of scratch vars etc.

But every time it happens we scratch our heads because we never really know where to hurt it.


Does anybody understand the metrics or can anybody offer any advice please?
Thanks!

Steve

MMSQL temporary tables

06 December 2010 - 08:40 PM

I need to create temporary data in msssql which I can then read in a proiv update or paging screen.

Creating the table and inserting into it is not a problem using

SQL
CREATE TABLE #TEMP
(
COL1 VARCHAR(2),
COL2 VARCHAR(30)
)

INSERT INTO #TEMP(COL1, COL2) VALUES('a',b)
ENDSQL


(at least I get no errors!)
but when I try to select and then subsequently read the selected entries by inserting

SELECT COL1, COL2 FROM #TEMP before the ENDSQL I get no records returned into the @F which corresponds to the file

Any suggestions please?

error in opening print file

12 September 2006 - 08:07 AM

We use bus and task and use PROIV reports to report back down the API - so in most we have the output set to API, but in some we use RPTOPT to achieve this.

Occassionally, we experience the dreaded error in opening print file error in the event viewer application log, and the task just ends - we don't know which report we are in or even why we got the problem.

Does anybody know what we can, either to resolve the problem, or in terms of defensive coding to at least trap and report the error back down the API?

Installing PROIV & the Client

28 July 2004 - 10:57 AM

I'm sure I'm not the only person with this issue..

We often need to release versions of PROIV and the client to our users, but most of them are not competent enough to do this on their own and get it right!

Is there a way of automating the procedure in a fool proof manner? We did experiment in using the install shield setup files but found that sometimes this did not work on site because of various factors.

Is there an easy/easier way to pre-configure all of the installation options so the client just runs an executable/batch file and it gets on with it?

How do other people get around this issue?

Thanks - Steve

Active X Client

16 January 2004 - 09:09 AM

Is anybody out there actually using the PRO-IV ActiveX Client (the ocx)?

If so, does it work and did you find it easy to implement?