error 19 - i'm stumped - snip [1/1] 
Author Message
 error 19 - i'm stumped - snip [1/1]

hi clipperheads

I think I have a pretty good stumper here.  It has me baffled anyway.

The following code snippet produces an error I have never had before but
I understand it to be a corrupted index and VNTX reports the same.

The actual error message reads   DBUNLOCK (0)  Internal Error 19

This only happens when there are more than one values for inacctno[addrecctr].

It also ceases when I un'rem the 'inkey(0)' line that is rem'ed.  Everything
appears to be in order so I am hesitant to believe it is the code.  I have used
this same structure in another program for years with no incidents at all.  I
am very confused at this point and could use the never-failing eye of some of
you gurus.  Any help would be greatly appreciated.

The code is as follows:

...
      SELECT GFGLGJDT
      FOR ADDRECCTR = 1 TO 8
? "xx" + inacctno[addrecctr] + "xx"
//inkey(0)
         IF LEN( ALLTRIM( INACCTNO[ADDRECCTR] ) ) > 0
            APPEND BLANK
            RETRY := .T.
            DO WHILE RETRY
               IF RLOCK()
                  RETRY := .F.
                  REPLACE ACCTNO    WITH INACCTNO[ADDRECCTR], ;
                          DEPT      WITH INVCHDEPT[ADDRECCTR],   ;
                          CR_DB     WITH INCR_DB[ADDRECCTR],  ;
                          AMT       WITH INAMT[ADDRECCTR],    ;
                          TRANSTYPE WITH "VC",        ;
                          BATCHNO   WITH INBATCHNO,   ;
                          DEPCHQNO  WITH INCLERK,     ;
                          TRANSCODE WITH "A/P VOUCH", ;
                          TRANSDATE WITH INVCHDATE,   ;
                          BATCHTYPE WITH "CD"
                  UNLOCK
                  COMMIT
               ELSE
                  ERRMESS( "That record is already in use! ", "Press any key to re-try. " )
               ENDIF
            ENDDO
         ENDIF
      NEXT

If more information is necessary, please email me and i will be happy to
oblige.

TIA

:-) owen
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Ultra Software (Owen Parker)        |  Ultra Software

                                    |  Dartmouth, N.S.
Phone  (Voice) 902 463 0243         |  B2Y 3W8
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"All work and no play makes you a computer consultant."
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



Mon, 29 Dec 1997 03:00:00 GMT  
 error 19 - i'm stumped - snip [1/1]

Quote:

> hi clipperheads

> I think I have a pretty good stumper here.  It has me baffled anyway.

> The following code snippet produces an error I have never had before but
> I understand it to be a corrupted index and VNTX reports the same.

> The actual error message reads   DBUNLOCK (0)  Internal Error 19

   Yes: this is a corrupted index.

Quote:
> The code is as follows:

[ snip ]
>                   UNLOCK
>                   COMMIT

[ snip ]

   You should COMMIT *before* you UNLOCK. Otherwise someone else
   can lock the record and start changing things before you've
   committed your changes to the DBF and associated indexes.

   This may be the cause of your problem:

--
- Matt Morris -



Mon, 29 Dec 1997 03:00:00 GMT  
 error 19 - i'm stumped - snip [1/1]

Quote:

>                   UNLOCK
>                   COMMIT

Should be...

Quote:
>                   COMMIT
>                   UNLOCK

COMMIT forces a disk write so everyone else can see it.
UNLOCK allows others to modify it.
Do the math.

Aloha from Vancouver, BC!

--
E ola mau ka `olelo Hawai`i!

Vote YES for Soc.Culture.Hawaii (Moderated)!
Strike a blow AGAINST Net-Terrorism!

Michael J. Wise
Vancouver, BC Canada
PGP Fingerprint = [80 FA 44 6B - C8 86 C1 2B - 70 0D 71 DE - A9 0C 62 85]



Mon, 29 Dec 1997 03:00:00 GMT  
 error 19 - i'm stumped - snip [1/1]

Quote:
>The following code snippet produces an error I have never had before but
>I understand it to be a corrupted index and VNTX reports the same.
>The actual error message reads   DBUNLOCK (0)  Internal Error 19

We've encountered the same error message, which occured at several
places of the program, where everything seemed to be ok.

The cause of the problem has been a previous call to the function
"fclose(fptr)", where fptr was an invalid filepointer (the file had
been already closed with a fclose before).

If you use the low-level functions fopen/fclose/fread..., be careful
about it. Maybe this could solve your problem.

roland



Tue, 30 Dec 1997 03:00:00 GMT  
 error 19 - i'm stumped - snip [1/1]


Quote:

>hi clipperheads

>I think I have a pretty good stumper here.  It has me baffled anyway.

>The following code snippet produces an error I have never had before but
>I understand it to be a corrupted index and VNTX reports the same.

>The actual error message reads   DBUNLOCK (0)  Internal Error 19

>This only happens when there are more than one values for inacctno[addrecctr].

>It also ceases when I un'rem the 'inkey(0)' line that is rem'ed.  Everything
>appears to be in order so I am hesitant to believe it is the code.  I have used
>this same structure in another program for years with no incidents at all.  I
>am very confused at this point and could use the never-failing eye of some of
>you gurus.  Any help would be greatly appreciated.

>The code is as follows:

>...
>      SELECT GFGLGJDT
>      FOR ADDRECCTR = 1 TO 8
>? "xx" + inacctno[addrecctr] + "xx"
>//inkey(0)
>         IF LEN( ALLTRIM( INACCTNO[ADDRECCTR] ) ) > 0
>            APPEND BLANK
>            RETRY := .T.
>            DO WHILE RETRY
>               IF RLOCK()
>                  RETRY := .F.
>                  REPLACE ACCTNO    WITH INACCTNO[ADDRECCTR], ;
>                          DEPT      WITH INVCHDEPT[ADDRECCTR],   ;
>                          CR_DB     WITH INCR_DB[ADDRECCTR],  ;
>                          AMT       WITH INAMT[ADDRECCTR],    ;
>                          TRANSTYPE WITH "VC",        ;
>                          BATCHNO   WITH INBATCHNO,   ;
>                          DEPCHQNO  WITH INCLERK,     ;
>                          TRANSCODE WITH "A/P VOUCH", ;
>                          TRANSDATE WITH INVCHDATE,   ;
>                          BATCHTYPE WITH "CD"
>                  UNLOCK
>                  COMMIT
>               ELSE
>                  ERRMESS( "That record is already in use! ", "Press any key to re-try. " )
>               ENDIF
>            ENDDO
>         ENDIF
>      NEXT

Hi There,

   There are many causes for an internal error 19 (Corrupt Index)
   One cause could be in the code snip you have provided.

   I Would uggest you try moving the COMMIT and UNLOCK statements around
   As This will Help Ensure Data Integrity and may solve the problem on its
   Own. ( Source, NG to clipper & many Frustrated Hours of hunting IE19 )

  Failing this, Check to see that ALL indexes are ALWAYS opened on the DBF
  when appending, packing, zapping, and changing Index Key data on existing
  records.

  Ensure that you have not opened the index twice in the same workarea.
  Clipper will allow you to do this and the effects are to cause an IE19,
  not on the initial save but the next time you do an update after the corruption
  occurs.

  Clipper 5 will sometimes trap Corrupt indexes through the errorsys, but
  will still get the IE19 In the last example above.

  Hope This Helps Some.

  Kurt Sharp, ITT Quotel.



Tue, 06 Jan 1998 03:00:00 GMT  
 
 [ 6 post ] 

 Relevant Pages 

1. Error message dbcommital internal error 19

2. Error: Internal Audit Error 19

3. Compile-mode for VHDL Compiler for emacs-19.19

4. Celefunt results, g77 0.5.19 vs 0.5.19.1

5. Internal Error 19

6. Internal Error 19

7. Internal Error 19

8. Internal error 19

9. Internal Error 19

10. DBSKIP(0) internal error 19

11. Internal Error 19

12. Internal error 19

 

 
Powered by phpBB® Forum Software