CALLX Not Working

#11

Cliff

Having just gone through my own CALLX issue (see the previous thread), I
was about to tell you Kevin's response about the the need for the fully
qualified path name.

Because CALLXs can be so frustrating ("is it my code or is it D3?") I
have found it useful to just put in a DEBUG or DISPLAY statement at the
beginning of the code, just to see if it is even being called or not.
That has at least pointed me in the right direction as to where the
problem lies.

Sholom

Cliff wrote:

Quote:

The fully qualified path worked! Thanks Kevin.

Thanks everyone for all of your help.

#12

Cliff wrote:

Quote:

The fully qualified path worked! Thanks Kevin.

I've gone through my own CallX frustrations in the past, so I'm glad I
could help.

--
Kevin Powick

#13

Cliff,

I'm just curious.

Does the file CLIFF.LOG exist? Did you create it
and is it in the user/account where you are running
the program?

If CLIFF.LOG does not exist, the OPEN will fail
and it will return immediately.

I can see no other potential reasons why your program
would not work.

Larry Hazel

"Cliff" <cponce (AT) easternmetal (DOT) com> wrote

Quote:

No, it was clear. I see the bug. I fixed it but still not working.

CLIFF.UPDATE
001 SUBROUTINE CLIFF.UPDATE(ITEM)
002 *
003 OPEN 'CLIFF.LOG' TO F.LOG ELSE RETURN
004 READ LOG.CNT FROM F.LOG,'LOG.CNT' ELSE LOG.CNT = 0
005 LOG.CNT = LOG.CNT + 1
006 WRITE LOG.CNT ON F.LOG,'LOG.CNT'
007 *
008 RETURN
009 *
010 END

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

CALLX Not Working

comp.databases.pick comp.databases.pick

Re: CALLX Not Working - 06-20-2006 , 08:53 AM

Re: CALLX Not Working - 06-20-2006 , 09:04 AM

Re: CALLX Not Working - 06-20-2006 , 10:44 AM