Internal Error 8002
your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 2 of 2 Thread: Clipper XP & Internal error 8002 Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 01-07-04,02:46 #1 tgf View Profile View Forum Posts Registered User Join Date Jan 2004 Posts 1 Unanswered: Clipper XP & Internal error 8002 I have a client who was succesffulyy running a Clipper application on Novell via DOS. They now want to run the same apllication using a Windows XP machine. However when re-indexing one of the larger files the internal error 8002 occurs. Can you advise me on what setting are required. Exospace is used in building the application. Reply With Quote 01-09-04,15:49 #2 Ida Hoe View Profile View Forum Posts Registered User Join Date Aug 2003 Location West Posts 101 Re: Clipper XP & Internal error 8002 I saw this ..... 8002 Indexing error While indexing, ordcreate(0) internal error 8002 may appear. It seems to appear mostly with CA-Clipper 5.3 programs linked with ExoSpace and running under Windows 95, although it has also been reported under Windows 3.1, and with CA-Clipper 5.2e and 5.01, and linked with Blinker. Typically, the error occurs on "larger" files (e.g. >10MB or 80,000 records), although that is not always the case. It has been reported that the 8002 error occurs unders the German version of CA-Clipper 5.3a during a section of code that opens and closes many tables repeatedly. When the error occurs with a Blinker-linked program under Win95, the program terminates with an Windows exception error. With an ExoSpace-linked program the 8002 error appears. The ExoSpace link option "EXOSPACE PACKAGE NOVM" disables the VMM system so that when Clipper uses up all available physical memory it will cause either error 8002 or "Conventional memory exhausted". It is not recommended for normal applications, although it may be appropriate for installation programs. Blinker has a similar link option available. Internal error 8002 may also be caused by an error in custom C or ASM code which allocates memory and then does not release it properly. The Windows memory system may interfere with CA-Clipper's Virtual Memory Manager, causing the error. It is not known whether the problem is limited to the DBFNTX RDD, or occurs in other (all) RDDs. Action: Try one or more of the following: 1) Try increasing the a
van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten
Equipe • Remover cookies deste fórum • Todos os Horários estão como internal error UTC - 3 horas [ DST ] Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Traduzido por internal error 8002 phpBB Brasil v Olá visitante, seja bem-vindo ao Fórum Clipper On Line!Efetue o seu login ou faça o seu Registro Sistema FCOL - Agora você pode acessar os tópicos, mensagens, anexos e arquivos da seção Downloads do Fórum Clipper On Line em modo OFF-LINE, sem qualquer conexão com a Internet. Clique aqui para mais detalhes.
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 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 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 d