Internal Error 5333 Clipper
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Computer Associates: Clipper Forum at Tek-Tips HomeForumsProgrammersDBMS PackagesComputer Associates: Clipper Forum Internal error 5333 thread288-344848 Forum Search FAQs Links MVPs Internal error 5333 Internal error 5333 Zbi (Programmer) (OP) 26 Aug 02 03:15 Can anybody tell me anything about the error above? It occurs on LOCATE command.Thank you in advance,Zbi RE: Internal error 5333 Elkari (Programmer) 26 Aug 02 10:18 From what I found out, it has to do with a NULL memory pointer or corrupted record indicator.Try packing the DBF you were trying to LOCATE into.This clean up should straighten up any record pointer problems. RE: Internal error 5333 circes9 (Programmer) 26 Aug 02 11:24 packing a corrupt database can be FATAL to your data. You may lose more than you expected.You may wish to browse your data and see what you can see before making any changes to it.Did this error occur in some new code or an existing program?This may give you a clue as to where to begin looking.Good luck RE: Internal error 5333 Elkari (Programmer) 26 Aug 02 11:35 Circes9 is right.If the DBF itself is corrupt, ie. it can't be openned due to header problems, then packing it would cause
deal? (Excellent reply contributed by David Husnian.) Clipper and most computer languages use a binary floating point format for their real numbers. This causes precision errors which commonly show up in calculations, comparisons and when rounding. The problem is related to trying to represent an infinite number of decimal numbers into a fixed number (and a small fixed number at that) of binary bits. Statistically, there aren't any numbers that can be represented exactly, of course, from a practical standpoint some can be (but they are all somehow related to powers of 2, like 1/2 or 3/8 or 127/128 or ...). Taking .275 out to just 16 bits yields: 0100011000100111 but that is really only .274993896484375. It http://www.tek-tips.com/viewthread.cfm?qid=344848 is impossible to represent .275 accurately in a binary numbering system, even with unlimited bits, let alone the 64 bits that Clipper uses (all of which aren't used for the decimal portion). Most modern languages use a format defined by the IEEE. An IEEE-compliant double precision implementation meets the following criteria: 1 sign bit, 52 bits for the mantissa and 11 for the exponent. 2.22 * 10 ^ -16 is the smallest number that, subtracted from 1.0, gives something http://www.davep.org/clipper/FAQ/clipper-5.html different than 1.0. Normalized to 1023, which means that 10 ^ 0 will be kept as 1023, with 10 ^ -1 as 1022 and 10 ^ 1 as 1024. Smallest useable floating value is 2.23 * 10 ^ -308. Largest useable floating value is 1.79 * 10 ^ 308. In the IEEE standard, rounding is considered to be finding the closest representable number to the "exact" number. Not an easy task, particularly at the level of Clipper. There are only two complete solutions: use only integers (for example, use 1234 to mean 12.34) or use a decimal numeric format like BCD. With Visual Objects you will be able to make variable declarations such as LOCAL i AS INT, which will have the effect of forcing only integer values into a variable. CA-Clipper 5.3a is compiled and linked with the 8.0 release of Microsoft C, including the standard math library component. The rounding problems under this library are likely to be somewhat less severe. 5.2 Why is "ABCDEF" = "ABC" turning up TRUE in my code? The single equal sign operator (=) is not what you expect. If you have SET EXACT OFF (the default) then string comparisons only check as far as the length of the right-side value. If you want an exact match, then you should use the double-equals operator (==) instead. Many programmers forget about it on purpose and just SET EXA
SEQUENCE/END Blocks 11 BEGIN SEQUENCE/END Integrity Error 12 Evaluation stack http://www.itlnet.net/programming/program/Reference/ierror/ng1c0.html underflow after BEGIN SEQUENCE/END 14 SORT Error 15 SORT Error 16 Database Not Open 17 NTX File Corrupted 18 NTX File Corrupted 19 NTX File Corrupted 20 NDX File Key Type Error 21 NDX File Key Type Error 22 NTX File Key Type Error 24 Write Error 92 SORT/INDEX ON Error 332 internal error String/Array memory overflow 415 Cannot open overlay file 416 Read error on dynamic page file 520 Attempt to get value for an invalid field type. 521 Replacement of field with invalid data type. 612 EVAL() given something other than codeblock. 650 Out of stack space 666 C Function Attempt to Free Invalid internal error 5333 Pointer 667 Eval stack crashed 668 Runtime error handler error 669 Cannot expand MEMVAR table 670 Memory initialization error 701 Unable to locate keyboard driver upon startup. 715 Printer not ready. 773 Dynamic overlay system not linked in. 999 Attempt to execute invalid code 1020 Record not found 1102 Requested RDD not linked 1210 Data and Index files out of sync 1242 Data type mismatch on key replacement 2155 Read error on index heading page 4406 Temp file read error 4412 Indexing miscalculation 4414 Indexing miscalculation 4424 Temp file creation error 5302 Conventional memory exhausted 5304 Conventional Memory Exhausted 5305 VM Swap Space Exhausted 5306 Conventional Memory Exhausted 5311 VMM Unable to Create Swap File 5312 VM Swap File Overallocated 5313 VMM Write Error on Swap File 5320 VMM IAMBS Manager Error 5333 Misuse of VM System This page created by ng2html v1.05, the Norton guide to HTML conversion utility. Written by Dave Pearson