?_%i l?mpt/Paradox Configuration HelpcBrowseButtons()ZsecondarybadmainQi2Z Qq50q5   Q6"QrEb##R+Phq5 .rEZsecondarysampleQi2Z Qq50q5   Q6"QrEs##R+Phq5{{/&;)z4F FuF  |CONTEXTa|CTXOMAPQ|FONTO|KWBTREEYQ|KWDATA/Q|KWMAPHQ|SYSTEM|TOPICT|TTLBTREEYEF_CONTENTS:010: 337: FFFF: 158 PX_APPENDIX:010: 2810: FFFF: 1060A PX_DLG_CONFIG:010: 1B1B: FFFF: 87B6 PX_OVERVIEW:010: 5B1: FFFF: 27A PX_OVERVIEW:020: CA1: FFFF: 1J(J 1=1= + $ Help Document Revision Notes ___________________________________________________________________________________________________b5=P- *jmpt/pxConfig Paradox Engine Configuration Tool,|$  NOTE:(P$  7|'   NEED TO ADD:[56& j Sorted Paradox Error List (See PX Error List.doc)(^%  M6. ,> Document Revisions1/4/04M'^& N Replicated from the EDiForm source&# 9W1zWCONTENTS}0 0Table of Contents ___________________________________________________________________________________________________2 W6& pxConfigL%' JParadox Engine Configuration Tool&6# nr\ eBM؀b3Ҁ OverviewProblems with ParadoxParadox Engine Configuration DialogParadox Error Codes&# 9r1 Overview< ( (BրParadox OverviewmHz% $_____________________________________________________________________ ?) 9Dր Mil-Pac applications use Paradox databases to manage many types of data seen by the user. Generally speaking, Paradox Engine configuration must be considered only whenever one or more of the following conditions apply:1) Databases are stored on a network and shared with others2) Databases are moved to a new location or machine3) Windows XP (or other versions requiring administrative rights) is used.Az% 8 Paradox Engine Lock FilesnI?% Dր Paradox creates two types of lock files in order to manage databases:  * "T!s NET files - are used to identify the various users of a database, so as to know who is using each record. These files, referred to as the Network Control Files, are named PARADOX.NET and PDOXUSRS.NET.LOCK files - are hold the current locks placed on database records by the various users identified by the NET files. The LOCK files keep users from changing the same records simultaneously. These files are named PARADOX.LCK and PDOXUSRS.LCK.- & Dր These lock files are created dynamically and can be deleted without problem, as long as the databases are not currently in use. In many cases, obsolete or invalid lock files are the source of database access errors and simply removing them solves the problem.[& ` 5 :LR!~ eSee Also:Problems With Paradox( % Dր C` 1nz KProblems; OverviewA ' 4 Problems with Paradox mH y % $_____________________________________________________________________n $  The Paradox Engine configuration must be considered whenever one or more of the following conditions apply:y )  1) Databases are stored on a network and shared with others2) Databases are moved to a new location or machine3) Windows XP (or other versions requiring administrative rights) is used.K' ?$ NȀ Sharing Databases on a Network DrivexPA( Fր Sharing databases used by Mil-Pac applications is fairly simple. First a network directory is defined that is accessible to all users. Then a drive ma?A pping is established using a traditional eight-character directory path names, such as M:\Shipping\DD250s. This is entered into the General Configuration Options of the application to be shared. Next the Paradox Engine must be told where to store its Network Control (.NET) File(s). This can be on any shared directory; one of shared application data directories will work just fine. This can be set with the Mil-Pac PXConfig Tool. \8?B$ pȀ Moving Databases to a New Machine or Network LocationAD3 4 Bր k[ Moving databases is simple, yet also the common cause of Paradox access errors. First it is important to remember that Paradox tables consist of at least two, and often three files, all with the same name. The extensions of these files are .PX, .DB and .MB. The FormStation directory consists of, for example, FS-IDX.PX, FS-IDX.DB and FS-IDX.MB. In some rare cases there will not be an MB file. It is important to move the entire set of files at the same time. The final step is remove the lock files., as they will cause the database to be inaccessible in its new location. The PXConfig Configuration Dialog can do this for you.BE& aBր These same steps should be followed when moving a database from a local drive to a network directory. First it is important to follow the steps on database sharing above. CDE$ >Ȁ Using Paradox on Windows XP 'EH' Bր Paradox-based applications such as Mil-Pacs work on Windows XP. However, if you are not are operating with administrator privileges, the default Paradox configuration must first be altered. This is something that is simple to do with PXConfig. The problem with Paradox and XP is that Paradox wants to store its Network Control (.NET) files in the root directory, which XP does not like, and in order to change that the application must change WIN.INI, something that XP allows only administrators to do. nHEH& Fր To solve these two problems, run PXConfig as the administrator, then:H}I* "T!s 1) Click on [Copy Data Path] which will tell Paradox to use the application database folder for its Network Control (.NET) files2) Click on [Remove Lock Files] to remove any persistent lock files. 4HJ& Bր Once the Paradox Engine is set to put its Network Control Files in other than the root directory, the application should work fine. Of course, locating the database and the Network Control Files on a shared network drive by following the steps above works as well. )}IJ& Fր (JK% Dր T#JVK1 VKParadox Engine Configuration DialogJ&KK$ L Paradox Engine Configuration DialogmHVK L% $_____________________________________________________________________KN9 @Dր The Paradox Engine Configuration dialog determines the current configuration of the Paradox Engine. It is accessed either through the Options | Paradox menu command on Mil-Pac applications, or by running the PXConfig utility, and selecting Find Appl DB.The values entered into this dialog are saved in WIN.INI. On operating systems that control access to WIN.INI, such as Windows XP, you must have administrator rights in order to make changes.5 LCN%  Dialog Fields+Nz8 >RW k[ Paradox Network Control File Directory is the location where Paradox will look for, and write to the .NET files used to coordinate table locking. This directory must be accessible to all users and applications which share Paradox databases. It must be a mapped drive using traditional eight-character path names, such as C:\DDFS\Data or M:\Shipping\DD250s. Use of C:\ is not recomCNzKmended, and in fact, not allowed in versions of Windows (i.e. XP) that control access to the root directory.DCNE XRW  Application Data Directory is the location that PXConfig believes your application data to be in. This is generally a suitable location for the Network Control File. You may use the [Copy Data Path] button to copy this directory path to the Paradox Network Control File Directory field.Open Tables is the maximum number of database tables that can be open at any one time. The allowable range is 1 to 64. A value of 9 is sufficient to allow for maximum efficiency of Mil-Pac software products.uzl9 @RW Record Buffers is the number of buffers allocated for movement of data between database records. The allowable range is 1 to 512. A value twice that of the Open Tables field is recommended.Swap Size determines the size of the swap buffer that serves as a cache. A larger cache decreases disk access but consumes additional memory. A value of 60 is recommended.4 ) "IButtonsblrp RW    k[ [Copy Data Path] copies the value from the Application Data Directory field to the Paradox Network Control File Directory field. .[Use Default Values] completes the dialog fields with the values recommended for Mil-Pac applications.[Remove Lock Files] deletes all of the Paradox lock files located in the Application Data Directory and the Paradox Network Control File Directory. These files are temporary in nature and are recreated by Paradox on a continual basis. Removing them often solves Paradox access issues. Be sure that all applications sharing Paradox data are closed.[&͇5 :LR!~ eSee Also:Problems with Paradox*r' PA~D͇;1X;Paradox Error Codes;v$ . Paradox Error Codes mH;% $_____________________________________________________________________v҉& Dր The Paradox Engine can generate a wide number of errors, depending on the type of operation being performed. In most cases, Mil-Pac users are likely to see only error numbers 15, 134, 12 or 118. FC Vo'Mq)O  u =҉U% 0Initialization Errors _L f}o'Mq)O  u PXERR_NOTINITERR 78 Engine not initializedPXERR_ALREADYINIT 82 Engine already initializedPXERR_NOTLOGGEDIN 98 Could not login on network (to PARADOX.NET)PXERR_NONETINIT 107 Engine not initialized with PXNetInitPXERR_NETMULTIPLE 15 Multiple PARADOX.NET filesPXERR_CANTSHAREPDOXNET 134 Can't lock PARADOX.NET, SHARE.EXE loaded?PXERR_WINDOWSREALMODE 135 Can't run Engine in Windows real mode?U% 4Hardware Related Errors_H ^5o'Mq)O  u PXERR_DRIVENOTREADY 1 Drive not readyPXERR_DISKWRITEPRO 124 Disk is write protectedPXERR_GENERALFAILURE 126 General hardware errorA% 8Directory Reg Error CodesS J bo'Mq)O  u PXERR_DIRNOTFOUND 2 Directory not foundPXERR_DIRBUSY 10 Sharing violationPXERR_DIRLOCKED 11 Sharing violationPXERR_DIRNOACCESS 12 No access to directoryPXERR_DIRNOTPRIVATE 14 Single user, but directory is shared<P% .File Oriented Errors/H ^o'Mq)O  u PXERR_FILEBUSY 3 File is busyPXERR_FILELOCKED 4 File is lockedPXERR_FILENOTFOUNP/D 5 Could not find file=Pl% 0Table Oriented ErrorsH/N jo'Mq)O  u PXERR_TABLEBUSY 118 Table is busyPXERR_TABLELOCKED 119 Table is lockedPXERR_TABLENOTFOUND 120 Table was not foundPXERR_TABLEOPEN 83 Unable to perform operation on open tablePXERR_TABLEINDEXED 94 Table is indexedPXERR_TABLENOTINDEXED 95 Table is not indexedPXERR_TABLEEMPTY 105 Operation on empty tablePXERR_TABLEWRITEPRO 22 Table is write protectedPXERR_TABLECORRUPTED 6 Table is corruptedPXERR_TABLEFULL 128 Table is full{1l/J bco'Mq)O  u PXERR_TABLESQL 130 Table is SQL replicaPXERR_INSUFRIGHTS 21 Insufficient password rightsPXERR_CANTUPGRADE 92 Table too old to upgrade, or existing table header too small.PXERR_LOCKTIMEOUT 137 Timed out trying to achieve a lock.=l% 0Index Oriented ErrorsK/L fo'Mq)O  u PXERR_XCORRUPTED 7 Primary index is corruptedPXERR_XOUTOFDATE 8 Primary index is out of datePXERR_XSORTVERSION 13 Sort for index different from tablePXERR_SXCORRUPTED 122 Secondary index is corruptedPXERR_SXOUTOFDATE 96 Secondary index is out of datePXERR_SXNOTFOUND 121 Secondary index was not foundPXERR_SXOPEN 123 Not used-here for backwards compatabilityPXERR_SXCANTUPDATE 136 Can't update table open on non-maintained secondary;l8F \vo'Mq)O  u PXERR_RECTOOBIG 125 Record too big for index>v% 2Record Oriented Errorsk8L f?o'Mq)O  u PXERR_RECDELETED 50 Another user deleted recordPXERR_RECLOCKED 9 Record is lockedPXERR_RECNOTFOUND 89 Record was not foundPXERR_KEYVIOL 97 Key violationPXERR_ENDOFTABLE 101 End of tablePXERR_STARTOFTABLE 102 Start of table7v% $Resource Errors-EK do'Mq)O  u PXERR_OUTOFMEM 40 Not enough memory to complete operationPXERR_OUTOFDISK 41 Not enough disk space to complete operationPXERR_OUTOFSTACK 127 Not enough stack space to complete operationPXERR_OUTOFSWAPBUF 129 Not enough swap buffer space to complete operationPXERR_OUTOFFILEHANDLES 70 No more file handles availablePXERR_OUTOFTABLEHANDLES 72 No more table handles availablePXERR_OUTOFRECHANDLES 103 No more record handles availableAI `go'Mq)O  u PXERR_OUTOFLOCKHANDLES 111 Too many locks on tablePXERR_NOMORETMPNAMES 86 No more temporary names availablePXERR_TOOMANYPASSW 115 Too many passwords specifiedG"E% DInvalid Parameters To Functions?AO lo'Mq)O  u PXERR_TYPEMISMATCH 30 Data type mismatchPXERR_OUTOFRANGE 31 Argument out of rangePXERR_INVPARAMETER 33 Invalid argumentPXERR_INVDATE 73 Invalid date givenPXERR_INVFIELDHANDLE 75 Invalid field handlePXERR_INVRECHANDLE 104 Invalid record handlePXERR_INVTABLEHANDLE 76 Invalid table handlePXERR_INVLOCKHANDLE 110 Invalid lock handlePXERR_INVDIRNAME 114 Invalid directory namePXERR_INVFILENAME 108 Invalid file name"O lo'Mq)O  u PXERR_INVTABLENAME 99 Invalid table namePXERR_INVFIELDNAME 74 Invalid field namePXERR_INVLOCKCODE 106 Invalid lock codePXERR_INVUNLOCK 109 Invalid unlockPXERR_INVSORTORDER 112 Invalid sort order tablePXERR_INVPASSW 116 Invalid passwordPXERR_INVNETTYPE 113 Invalid net type (PXNetInit)PXERR_BUFTOOSMALL 117 Buffer too small for resultPXERR_STRUCTDIFFER 81 Table structures are differentFE Zo'Mq)O  u PXERR_INVENGINESTATE 79 Previous fatal error; cannot proceed8% &Blob Error CodesGL fo'Mq)O  u PXERR_BLOBMODE 51 Operation not applicable for Blob's open mode.PXERR_BLOBOPEN 52 Blob already open.PXERR_BLOBINVOFFSET 53 Invalid offset into Blob.PXERR_BLOBINVSIZE 54 Invalid size for Blob.PXERR_BLOBMODIFIED 55 Another user modified Blob.PXERR_BLOBCORRUPT 56 Blob file corrupted.PXERR_BLOBNOINDEX 57 Cannot index on a Blob.PXERR_BLOBINVHANDLE 59 Invalid Blob handle.BE Zo'Mq)O  u PXERR_BLOBNOSEARCH 60 Can't search on a Blob field.N)% RErrors Specific For Windows Engine DLLYrE Zo'Mq)O  u PXERR_TOOMANYCLIENTS 131PXERR_EXCEEDSCONFIGLIMITS 132PXERR_CANTREMAPFILEHANDLE 133<- *R!~ See Also:1r1X'$  1717 2 i%  R Lock FilesnI7% Dր Paradox creates two types of lock files in order to manage databases: i* "T!s NET files - are used to identify the various users of a database, so as to know who is using each record. These files, referred to as the Network Control Files, are named PARADOX.NET and PDOXUSRS.NET.LOCK files - are hold the current locks placed on database records by the various users identified by the NET files. The LOCK files keep users from changing the same records simultaneously. These files are named PARADOX.LCK and PDOXUSRS.LCK.6  - (LR These lock files are created dynamically and can be deleted without problem, as long as the databases are not currently in use. In many cases, obsolete or invalid lock files are the source of database access errors and simply removing them solves the problem.11DHelvLE=mpt/Paradox $ guration Help CENDIXS=CONTENTS [W$$0$00  /&;)i248F&DConfigurationDialogsErrorsParadox FV ;V~|;FvFVFVF&9T} &9D sFt FuF Fu+v v+P+ɃQWf2FV u0& FދΉFF V&&WNjFV&G&W+&G&G FV&G&W F$&G~F tF PWvQU0& ƋV(0&^F t 0& 0& +^_] UV+ɋF VV‹&GtRVv vv:=؋ 0& ~ u u F&d vv 40& ^] UvvP+PPy]Uvv+PPP`]UWVvF&|u}&t&t&D$<%Pǚp#>Ž&D=u0&^0& +LF&t+PPP&g |=s 0& ώF&t+PPP&0& ^_]UWVŽv ~} ÎF&D &TFV&;T |,&;Dv$&D&T &+D &TFV  | u+&Dt&|+FFFÎAFÎ&&TVRP uF&F&D&TFVW&D &TȋFV RP+PN^&ËN^+N^ut%ظD&>^u  &^ Wv v vv# ‰FV0&^0& |FF&D &TFV^_] UVv F tHtHtFF#FV D TDT FV FV~|FVD TŽ& FFĎ& FVUĎ^] 0& ːUFWVFF~} ~s~ FV F &9U} &9E s&uvv+P&;Ft;VtF &uFP RP#= ty tr 0^F&F &uFċVƉFމV&M &]+ډ~F;Nu ;^u+F^&G&W FV=u;u9V}~9FstVRP+P&;Ft;VtVFPRP#D=t tvFVFV=u;uFV9V}9Fr~tFVFV~֍vЎFVFVvRP+Q&a;Fu$;VuvFPRP#H=u uq0&^F u=^&4FVFVFVFVFN^N^;uP;uLFVFVFVFV~t3FvFVFV=u;t+Fv*FFVFVFV^ &G&W F~tZVvv&^& tg~ FVF &E &U~u~uF &E&E FFFVFV;FuX;V/&;)Lzu00&^ s XCONTENTSzOverviewProblems; OverviewParadox Engine Configuration Dialog Paradox Error Codes'*IF+Fy+F;~PnjFRPv v Rm0 +vFt<ߎF^&?t.F+Fy+F;~PnjFRPv v Re/ +vFt<ߎF^&?t.F+Fy+F;~PnjFRPv v R0 +vFt:ߎF^&?t,PW~F욺0VFVFRPv v R/ F V ^_] UVv F t&NF tFPQF PV0=+^]UWV~vv+1F&5^&7+FF^ &^&vvN ^Y*=\twL,.t t, t'>F&55FDF &FF&^&D^&F &F^8uY,؃~u ^&7^ &?.u FF&^_]UVv vv6V u!P*PP`3U2PX1ƋV^]UVFVFV |-=v&PFRPWO2 P5I2V u+XFVF&&TމNvNFVF @t&FVn^ tvFsF &ڋËV^]UWV^ F&&W uT=wOFV u?=w:FPVN2V tFVF&&Tƌ +v vvV tF~FF VFVFVF&9Twr&9s &&TFV~u ~u++FN^ uv+۹;r w;vӋ+ɻ+N;r w;vӋFVRPvvvv!. +NNF|4F+NNFN%FFV)FVZvv .NjV^_] Uvv v vv] UV^F&&W u=v vVHO5 vV 5p3^]UVv vVv vvV u!P*PP`3O5P4ƋV^] UWV~v F&*+RPWF & *ΌRQ~Fǚ!X4 ^&&Ƌ^_]UWV~ v&*FF&*"F&*F u FGF~u1؀~t} ~| ~+^_]UWVvF&F*+RPDQPQV!5 ^*&8Ƌ^_]UWVvFPVC5*+RPWVDWPN!P6 NJF&ƌ^_]UWVv ~^ F&8u <t!FG&*6*6:*u:tFG吸6+"5؎F &***F&**+^_]UWVv ~^ F&8u t FG&*6+6:+u:tFG吸m7+"6؎F &*/&;)L4^_]Uzb3 BMضU%ck[*e  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`ABCDEFGHIJKLMNOPQRSTUVWXYZ{|}~AAAEEEEIIIIOOOUUUYTMP\\.\\L U/2/(/*/,/./0/&//4/6/V@/PH/J/D/:/F/N/P/L/R/\/T/V/Z/X/`/b/d/f/h/j/p/l/v/x/z/n/r//t/|////~////////////////////////////////////J//////////  /R ////////000/00 0 000000000 0&0"0$0,0(0*0.0<>R6000 - stack overflow R6003 - integer divide by 0 R6008 - not enough space for arguments R6009 - not enough space for environment run-time error R6002 - floating-point support not loaded R6001 - null pointer assignment "/600)/& F&D,&T.&D0&T2W&D HPVV t͉~vV VRPvVPoF FtƙRPvWvv!r vWvvFF F tFRPFPWv v !k ^F tFF&&G&G+/& ^_]UWV^F&G$& G"u"^F tF&+&G&GDF&|&D.& D,u)Vds t^F tF&/& F&D,&T.&D0&T2W&D HPVFV tʉ~vV V+'vVvvP6svVvvG^&GH;Ή~FPVvv+PHqF FtǙRPvVvv!s ƋVRPvvRFF F tFRPƋVRPv v !q ^F tFF&+v&wF&G+/& ^_]UWV^F& F&D.& D,uVdot t /& F&D,&T.&D0&T2^&7&L IQPV1FV tv^&GFVVF F t