{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "EXTRAS PAK", "size": 879149, "date": "1994-02-03", "time": "7:25" }, { "name": "INSTALL DBF", "size": 6734, "date": "1994-02-03", "time": "7:28" }, { "name": "INSTALL EXE", "size": 64351, "date": "1993-10-04", "time": "19:50" }, { "name": "INSTALL FPT", "size": 3840, "date": "1994-02-03", "time": "7:28" }, { "name": "INSTALL INI", "size": 149, "date": "1994-02-02", "time": "6:19" }, { "name": "INSTALL TXT", "size": 8912, "date": "1994-01-14", "time": "14:16" }, { "name": "PRO PAK", "size": 243432, "date": "1994-02-03", "time": "7:25" }, { "name": "PRO2 PAK", "size": 181054, "date": "1994-02-03", "time": "7:25" }, { "name": "PSSKB TXT", "size": 33822, "date": "1994-01-14", "time": "14:16" }, { "name": "README TXT", "size": 22188, "date": "1994-01-14", "time": "14:16" } ] } ], "volume": "5E040D0B2E0" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "EXTRAS2 PAK", "size": 33606, "date": "1994-02-03", "time": "7:26" }, { "name": "FOXHELP PAK", "size": 726893, "date": "1994-02-03", "time": "7:26" }, { "name": "PRO2 PA1", "size": 695447, "date": "1994-02-03", "time": "7:25" } ] } ], "volume": "5E040D0B2E3" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "COMMFUNC PAK", "size": 131685, "date": "1994-02-03", "time": "7:26" }, { "name": "EXTRAS2 PA1", "size": 137500, "date": "1994-02-03", "time": "7:26" }, { "name": "FNDATION PAK", "size": 82549, "date": "1994-02-03", "time": "7:26" }, { "name": "PROX PAK", "size": 1103786, "date": "1994-02-03", "time": "7:26" } ] } ], "volume": "5E0407091B2" }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "DEMO PAK", "size": 127049, "date": "1994-02-03", "time": "7:27" }, { "name": "FNDATION PA1", "size": 110353, "date": "1994-02-03", "time": "7:26" }, { "name": "FOXDOC PAK", "size": 113485, "date": "1994-02-03", "time": "7:27" }, { "name": "SAMPLE PAK", "size": 1023085, "date": "1994-02-03", "time": "7:27" }, { "name": "TUTORIAL PAK", "size": 79874, "date": "1994-02-03", "time": "7:27" } ] } ], "volume": "5E040D0B352" }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "FOXAPP PAK", "size": 231389, "date": "1994-02-03", "time": "7:28" }, { "name": "FOXDOC PA1", "size": 106644, "date": "1994-02-03", "time": "7:27" }, { "name": "GENGRAPH PAK", "size": 32127, "date": "1994-02-03", "time": "7:27" }, { "name": "HELPTREE PAK", "size": 8041, "date": "1994-02-03", "time": "7:27" }, { "name": "LASER PAK", "size": 270956, "date": "1994-02-03", "time": "7:28" }, { "name": "LCKUPDT PAK", "size": 96019, "date": "1994-02-03", "time": "7:28" }, { "name": "PDRIVERS PAK", "size": 139136, "date": "1994-02-03", "time": "7:28" }, { "name": "PIECES PAK", "size": 16117, "date": "1994-02-03", "time": "7:28" }, { "name": "PROCOLOR PAK", "size": 66423, "date": "1994-02-03", "time": "7:28" }, { "name": "SNIPFMT PAK", "size": 21183, "date": "1994-02-03", "time": "7:28" } ] } ], "volume": "5E040D0B373" } }, "desc_file": "README.TXT", "desc_text": " README.TXT\r\n**********************************************************\r\n Release Notes for\r\n \r\n Microsoft(R) FoxPro(R) for MS-DOS (R) Version 2.5b\r\n\r\n (C)1993 Microsoft Corporation. All Rights Reserved.\r\n\r\nInformation in the FoxPro online Help is more current than\r\ninformation in the printed documentation. This README\r\nprovides information not contained in the FoxPro online\r\nhelp or documentation, and provides corrections to both.\r\n**********************************************************\r\n========\r\nCONTENTS\r\n========\r\n\r\nPart Description\r\n---- -----------\r\n1 Installation\r\n2 WAIT...WINDOW Enhancements\r\n3 New Commands and Functions\r\n4 New Transporter and Screen Directives\r\n5 International and Cross-Platform Recommendations\r\n\r\n----------------------------------------------------------\r\n====================\r\nPart 1: Installation \r\n====================\r\n\r\nThere are three types of installation for FoxPro for\r\nMS-DOS: Normal Installation, Administrative Installation\r\nand Workstation Installation. Instructions for Normal\r\nInstallation are in the FoxPro Installation and\r\nConfiguration manual. For information about Administrative\r\nand Workstation Installation, see INSTALL.TXT on FoxPro \r\nfor MS-DOS Disk 1.\r\n----------------------------------------------------------\r\n================================\r\nPart 2: WAIT WINDOW Enhancements \r\n================================\r\n\r\nWAIT WINDOW now supports multiple line messages. Use a\r\ncarriage return (CHR(13)) to move portions of your message\r\nto additional lines. The message window is automatically\r\nexpanded to accommodate additional lines. For example, this\r\ncommand creates a message window that contains two lines:\r\n\r\nWAIT WINDOW \"This is the 1st line\" + CHR(13) + ;\r\n \"This is the 2nd line\"\r\n\r\nThe width of the message window is adjusted to fit the\r\nlongest line in the message. All lines in the message are\r\nleft justified in the message window. Line feeds (CHR(10))\r\nfollowing CHR(13) are ignored.\r\n----------------------------------------------------------\r\n==================================\r\nPart 3: New Commands and Functions \r\n==================================\r\n\r\nSeveral new commands and functions are added to\r\nFoxPro 2.5b. For additional information about these\r\ncommands and functions, see the \"International and Cross\r\nPlatform Recommendations\" section below and the\r\ncorresponding topics in Help.\r\n\r\nNew Commands\r\n------------\r\n\r\nSET NOCPTRANS\r\nSET COLLATE\r\n\r\nNew Functions\r\n-------------\r\n\r\nCPCURRENT( )\r\nCPDBF( )\r\nCPCONVERT( )\r\nIDXCOLLATE( )\r\n----------------------------------------------------------\r\n=============================================\r\nPart 4: New Transporter and Screen Directives \r\n=============================================\r\n\r\nSeveral new Transporter and screen directives have been\r\nadded.\r\n\r\nThe #DOSOBJ, #MACOBJ, #UNIXOBJ and #WINOBJ \r\nTransporter directives allow you to transport objects\r\ncreated in the Screen Builder and Report Writer to \r\nspecific FoxPro platforms. For additional information \r\nabout these Transporter directives, see the Transporting \r\nFiles topic in Help.\r\n\r\n#TRAN SNIPPET ONLY, a new screen directive, is available\r\nin FoxPro 2.5b. This screen directive affects how screen\r\nobjects are transported, and is not discussed in Help.\r\n#TRAN SNIPPET ONLY is designed to limit the Transporter's\r\nchanges to just screen snippets, and is placed in\r\na screen's Setup snippet.\r\n\r\nWhen screen objects are transported to a different FoxPro\r\nplatform, only the screen snippets for updated screen\r\nobjects are transported if #TRAN SNIPPET ONLY is included.\r\nAll other screen object attributes are not transported to\r\nthe different platform. \r\n\r\nNote that #TRAN SNIPPET ONLY only affects updated screen\r\nobjects; it does not affect new or unchanged screen\r\nobjects or screen objects being transported for the first\r\ntime.\r\n----------------------------------------------------------\r\n=========================================================\r\nPart 5: International and Cross Platform Recommendations \r\n========================================================= \r\n\r\n *** IMPORTANT ***\r\n\r\n*******************************************************\r\n* Be sure to read this section completely before you *\r\n* change code pages or collation sequences! *\r\n*******************************************************\r\n\r\nOverview of topics\r\n\r\n1 FoxPro Collation Sequences\r\n2 Case-Insensitive Collation Sequences\r\n3 Case-Sensitive Collation Sequences\r\n4 How do the SEEK and SKIP commands work?\r\n5 Alternatives to SEEK and SKIP\r\n6 Additional Recommendations\r\n7 New Code Pages\r\n8 CPZERO Program\r\n9 Corrections to the Help File\r\n\r\nFoxPro 2.5b gives international developers and users\r\npowerful new features for handling accented characters\r\nacross different FoxPro platforms, and provides \r\naccurate sorting in many languages.\r\n\r\nFor international FoxPro users, this section describes\r\nhow code pages and collation sequences affect sorting,\r\nseeking and comparisons using the SORT and SEEK commands,\r\nand also provides recommendations for taking advantage\r\nof these features.\r\n\r\nU.S. FoxPro users whose applications don't contain\r\naccented characters may not need any of the new\r\ninternational 2.5b features. In this case, you can\r\ndisregard this section of the README and the\r\nInternational/X-Platform topic in Help. FoxPro 2.5b is\r\n100% percent compatible with FoxPro 2.5. \r\n\r\n1 FoxPro Collation Sequences\r\n----------------------------\r\n\r\nWith a MACHINE collation sequence, which earlier FoxPro\r\nversions use (and to which FoxPro 2.5b still defaults),\r\neach character in the code page, whether it's a Roman\r\ncharacter, an accented character, or a line-drawing\r\ncharacter, has a unique \"sort weight\" determined by its\r\nposition in the code page. In a majority of code\r\npages, all accented characters appear after the unaccented\r\ncharacters. In this situation an ä sorts after z, which\r\nisn't correct in most languages (although it is true in\r\nSwedish, for instance).\r\n\r\nFurthermore, in most languages accented characters sort\r\nafter their unaccented counterparts, but only if the\r\nunaccented versions of all characters being compared are\r\nthe same. For example, in German, ä sorts after the\r\nunaccented a, but the string äa sorts before the string ab\r\nbecause the second character a is less than the second\r\ncharacter b. In this way, characters are interleaved in\r\nmany cultures.\r\n\r\nFoxPro 2.5b supports a number of new collation sequences\r\nto correctly sort in many languages. These sequences take\r\ninto account all the complex rules of the language\r\n(including two-to-one, three-to-one and one-to-two\r\nmappings). The following collation sequences were\r\navailable when this README was created. The code pages\r\nfor which these collation sequences are defined are also\r\nincluded.\r\n\r\nCollation Sequence Friendly Name Code Pages\r\n------------------ ------------- ----------\r\nCZECH Czech 852, 895, 1250\t\t\t\r\nDUTCH Dutch 437, 850, 1252\r\nGREEK Greek 737, 1253\t\t\t\r\nGENERAL General 437, 620, 850,\r\n 852, 861, 865,\r\n 895, 1250, 1252,\r\n 10000\t\t\t\r\nHUNGARY Hungarian 852, 1250\t\t\t\r\nICELAND Icelandic 437, 850, 861,\r\n 1252\r\nMACHINE Machine All\t\t\t\r\nNORDAN Norwegian/Danish 437, 850, 865,\r\n 1252\t\r\nPOLISH Polish 620, 852, 1250\t\t\t\r\nRUSSIAN Russian 866, 1251\t\t\t\r\nSLOVAK Slovak 852, 895, 1250\t\t\t\r\nSPANISH Spanish 437, 850, 1252\r\nSWEFIN Swedish/Finnish 437, 850, 1252\r\nUNIQWT Unique Weight 437, 850, 1252,\r\n 10000\t\r\n\r\nIf you specify a collation sequence in the SET COLLATE\r\ncommand as a string literal, enclose the collation\r\nsequence in quotation marks. Don't enclose the collation\r\nsequence in quotation marks if you specify a collation\r\nsequence in your FoxPro configuration file (CONFIG.FP or\r\nCONFIG.FPW).\r\n\r\nIf you use the SET COLLATE command to specify a collation \r\nsequence that isn't supported by the current code page, \r\nFoxPro generates an error. If you specify a collation \r\nsequence in your FoxPro configuration file that isn't \r\nsupported by the current code page, the collation sequence \r\ndefaults to MACHINE.\r\n\r\nIf you specify a collation sequence in the International\r\npanel in the View window, the collation sequence names \r\nappear in longer forms. For example, the NORDAN option \r\nappears as Norwegian & Danish, and the SWEFIN option \r\nappears as Swedish & Finnish.\r\n\r\nFor additional information about collation sequences, see\r\nSET COLLATE in Help.\r\n\r\n3 Case-Sensitive Collation Sequences\r\n------------------------------------\r\n\r\nTwo case-sensitive collation sequences are available in\r\nFoxPro: the familiar MACHINE sequence, the default\r\nsequence in earlier FoxPro versions, and the sequence\r\nnamed UNIQWT. UNIQWT is a \"unique weight\" sort in which \r\neach accented character sorts strictly after its \r\nunaccented counterpart (unlike the interleaving of \r\naccented characters described earlier).\r\n\r\nWhile the collation sequence with UNIQWT isn't strictly\r\nculturally correct as with GENERAL, it may aid developers\r\nin migrating their applications from earlier FoxPro\r\nversions. One reason is that upper- and lower-case letter\r\nare treated distinctly as they were in earlier FoxPro\r\nversions. Another reason is described in the section\r\ntitled \"How do the SEEK and SKIP commands work?\"\r\n\r\n4 How do the SEEK and SKIP commands work?\r\n-----------------------------------------\r\n\r\nThe SEEK command accepts an expression. FoxPro transforms\r\nthat expression into a sort key which it compares to\r\nkeys in the master index or tag. SEEK then positions the \r\nrecord pointer at the first index entry that's greater \r\nthan or equal to ( >= ) the supplied key.\r\n\r\nWith a machine sort, SEEK finds a match if there is one.\r\nThe UNIQWT sort has the same property. But when FoxPro\r\nuses the new language-specific collation sequences to\r\ncreate indexes, only the alphabetic part of the key is\r\nconsidered and any diacritical marks are ignored. In other\r\nwords, even if you SEEK \"äbc\" you may find \"abc\". Note\r\nthat partial searches (where you search for part of the\r\nfield) using SEEK may not return the results you expect\r\nwhen the current collation sequence is not MACHINE or\r\nUNIQWT.\r\n\r\nFoxPro behaves this way for the following three reasons:\r\n\r\n1) Performance.\r\n\r\n2) Consistency with the SKIP command.\r\n\r\n3) Consistency with the SET NEAR command.\r\n\r\nTo have SEEK and SKIP find only those records that exactly\r\nmatch accented characters, you must either SET EXACT ON or\r\nuse an index tag created with the MACHINE or UNIQWT\r\ncollation sequences. \r\n\r\nNote that SEEK and SKIP use the collation sequence of the\r\nmaster index or tag, and ignore the current collation\r\nsequence. SEEK can't be used unless there is an index is\r\nactive. \r\n\r\n5 Alternatives to SEEK and SKIP\r\n-------------------------------\r\n\r\nIf you use accented characters, use one of the following\r\nmethods to search a table:\r\n\r\n1) Construct a loop with SCAN FOR ... ENDSCAN.\r\n\r\n2) Use LOCATE FOR ... CONTINUE. \r\n\r\nLOCATE and SCAN use an index if one is active, and\r\nthey have two very significant advantages over SEEK when\r\ndata contains accented characters.\r\n\r\nFirst, both LOCATE and SCAN remember the condition with\r\nwhich they were invoked, so they can be used for looping\r\non a condition. SEEK, on the other hand, simply positions\r\nyou somewhere in the index, and SKIP continues down the\r\nindex from that point. With international data, this may\r\nnot give you the results you want.\r\n\r\nSecond, LOCATE and SCAN are diacritically-sensitive,\r\nwhereas SEEK isn't. In addition, both LOCATE and SCAN can\r\nbe fully optimized by Rushmore if the current collation\r\nsequence is MACHINE or UNIQWT; otherwise partial\r\noptimization will occur.\r\n\r\nThe ORDER BY clause of the SQL SELECT command uses the\r\ncurrent collating sequence, which is returned by\r\nSET(\"COLLATE\")).\r\n\r\n6 Additional Recommendations\r\n----------------------------\r\n\r\n1) If you aren't concerned with indexing accented\r\ncharacters in a language-specific way, feel free to\r\ncontinue to use machine indexes. For many U.S. users,\r\nthis is appropriate.\r\n\r\n2) For the best performance when using a collation\r\nsequence other than MACHINE or UNIQWT, be sure that the\r\ncurrent collation sequence is the same as the collation\r\nsequence of any indexes you are using.\r\n\r\n3) Most international users will want accented characters\r\nin all fields to be translated automatically by FoxPro\r\nwhen running cross-platform applications. However, if you\r\nhave a table with a character field that's actually \r\nstoring binary information (data), the SET NOCPTRANS \r\ncommand allows you to inform FoxPro that characters\r\nin such a field should not be translated. \r\n\r\nBinary data might otherwise be changed, because of\r\nFoxPro's \"nearest\" character mapping. For characters such\r\nas the MS-DOS line-drawing characters, FoxPro maps to the\r\n\"nearest\" character in the destination code page.\r\n\r\nIf you choose to use SET NOCPTRANS, you must do so\r\nimmediately after issuing the USE command. From that\r\npoint on, FoxPro's automatic character translation is\r\nnot in effect for any fields you designate. In particular, \r\nyou must issue the SET NOCPTRANS command before issuing \r\na SQL SELECT command -- you cannot let SQL SELECT open\r\ntables for you if the tables contain fields which should\r\nnot be translated.\r\n\r\nNote that SET NOCPTRANS only operates on fields for the\r\ntable open in the currently selected work area. If you\r\nclose a table and then open the table again, you must\r\nreissue SET NOCPTRANS and designate the fields which\r\nshould not be translated.\r\n\r\n4) If you create cross platform applications, you should\r\navoid using FoxFont. FoxFont is an OEM MS-DOS font that\r\nyou may find useful in some situations. But if you use\r\nFoxFont in an application you create in FoxPro for\r\nWindows, some of the characters in the application may\r\nnot transport correctly to other FoxPro platforms.\r\n\r\nFurthermore, FoxFont won't correctly display characters\r\ntyped on international Windows keyboards. If you have\r\nautomatic code page translation enabled, FoxPro will\r\ndisplay accented characters correctly.\r\n\r\nFoxFont is the installed default font for the FoxPro\r\ndesktop. FoxFont is the default font for user-defined\r\nwindows created with DEFINE WINDOW when the FONT clause\r\nis omitted. Be sure to include the FONT clause when\r\ncreating user-defined windows in FoxPro for Windows.\r\n\r\nFixedSys is the default font for the Command, Trace and\r\nDebug windows if you're using Windows 3.1. Text editor\r\nwindows default to the current Command window font. \r\n\r\n5) FoxPro 2.5b can automatically translate accented\r\ncharacters in most files types such as .DBF, .SCX, and\r\n.FXP files. However, program (.PRG) and text (.TXT)\r\nfiles don't have a header and can't be marked with a code\r\npage. Therefore, FoxPro must assume that a program or text\r\nfile was designed for use on the platform on which it is\r\nopened.\r\n\r\nIt's important that you compile each program on the \r\nplatform on which it was written. Since compiled programs \r\n(.FXP files) have a header, once you compile a program, it \r\ncan be run on any FoxPro platform and accented characters \r\nin the original source program are automatically \r\ntranslated when automatic code page translation is in \r\neffect.\r\n\r\n6) Do not mix programs created on different FoxPro\r\nplatforms in a project. The Project Manager assumes that\r\nall programs in a project are native to the current FoxPro\r\nplatform. If you create an application or an executable\r\nfrom a project that contains programs created on different\r\nFoxPro platforms, translation of accented characters in\r\nthe programs might not be translated properly.\r\n\r\nAlso, within the Project Manager you can't specify the\r\nplatform on which a program or text file was created.\r\nTherefore, in the Project Manager don't edit programs or\r\ntables created on a FoxPro platform other than the current \r\nplatform. This means that you shouldn't double-click on a\r\nfile to open it in the Project Manager if you've enabled\r\nautomatic translation by including CODEPAGE = AUTO in \r\nyour FoxPro configuration file.\r\n\r\nIf you create an application that contains files created\r\non different FoxPro platforms, do not open the files for\r\nediting from within the Project Manager.\r\n\r\nHowever, once you build an application (.APP file), it\r\nwill run on any FoxPro platform and FoxPro can\r\nautomatically translate accented characters.\r\n\r\n7) If you have a project created in FoxPro for MS-DOS\r\nversion 2.0 and the files within the project contain \r\naccented characters, you can share the project and \r\nits files across different FoxPro platforms by performing\r\nthe following steps to convert the project and its files.\r\nThis conversion is required just once, and enables cross \r\nplatform sharing of all the elements of the project.\r\n\r\na) Open the project in FoxPro for MS-DOS 2.5b or FoxPro\r\n for Windows 2.5b. A dialog appears, asking if you would \r\n like to convert the project to a 2.5 format. Choose \r\n Yes, then close the project.\r\n \r\nb) Open every screen, report, label, menu and table\r\n contained in the project with the USE command. You are \r\n prompted for the code page (437, 850 and so on) on \r\n which each was created. Specify the MS-DOS code page \r\n on which each was built and then choose Yes.\r\n\r\nc) Use MODIFY COMMAND or MODIFY FILE and include the\r\n AS clause to open EVERY program, query, format file\r\n or text file contained in the project. In the AS\r\n clause, specify the code page (437, 850 and so on)\r\n of the FoxPro platform on which each was created.\r\n Choose the Save As option from the File menu and choose\r\n the Change Code Page check box. In the dialog that\r\n appears after you choose Save, specify the code page\r\n for the FoxPro platform on which the file will be used.\r\n\r\n8) If you're developing a cross-platform application,\r\navoid using characters that appear in one code page and\r\nnot another. For example, the MS-DOS line drawing\r\ncharacters aren't supported under Windows, so avoid using\r\nthem in screens you plan to transport between FoxPro for\r\nMS-DOS and FoxPro for Windows.\r\n\r\nYou can use CHR() if your application absolutely requires\r\nline drawing and accented characters. Output from CHR()\r\nisn't translated when the function is executed, allowing\r\nyou to output any character.\r\n\r\n9) The MS-DOS file system is case-insensitive and requires\r\nuppercase file names. If your applications run on FoxPro\r\nfor MS-DOS, be sure to restrict file names to those\r\ncharacters that have uppercase equivalents in your MS-DOS\r\ncode page.\r\n\r\nFor example, code page 437 doesn't contain uppercase\r\nversions of several accented vowels. These characters\r\ncan't be safely used in a FoxPro file name. It's best\r\nto avoid accented characters in file names.\r\n\r\n7 New Code Pages\r\n----------------\r\n\r\nThe following code pages are now supported:\r\n\r\nCode Page Platform\r\n--------- --------\r\n437 U.S. MS-DOS\r\n737 Greek MS-DOS (437G)\r\n620 Mazovia (Polish) MS-DOS\r\n850 International MS-DOS\r\n852 EE MS-DOS (Latin II)\r\n861 Icelandic MS-DOS\r\n865 Nordic MS-DOS\r\n866 Russian MS-DOS\r\n895 Kamenicky (Czech) MS-DOS\r\n1250 Windows EE\r\n1251 Russian Windows\r\n1252 Windows ANSI\r\n1253 Greek Windows\r\n10000 Standard Macintosh\r\n\r\nByte 29 in table headers contains the code page identifier.\r\nThe following table lists the code page and the\r\ncorresponding code page identifier in hex.\r\n\r\nCode Page Code Page Identifier\r\n--------- --------------------\r\n437 x01\r\n737 x6A\r\n620 x69\r\n850 x02\r\n852 x64\r\n861 x67\r\n865 x66\r\n866 x65\r\n895 x68\r\n1250 xC8\r\n1251 xC9\r\n1252 x03\r\n1253 xCA\r\n10000 x04\r\n\r\n8 CPZERO Program\r\n----------------\r\n\r\nIf you accidentally specify the wrong code page when\r\nyou open a table that isn't marked with a code page, run\r\nCPZERO.PRG to reset the table's code page to zero. CPZERO\r\nis a FoxPro program that is automatically installed in\r\nyour FoxPro directory. Before you run CPZERO, make sure\r\nthat the table whose code page you'll reset isn't open.\r\nWhen you run CPZERO, you are prompted for the name of the \r\ntable to modify. \r\n\r\n9 Corrections to the Help File\r\n------------------------------\r\n\r\nConfiguring FoxPro and International/X-Platform Topics\r\n------------------------------------------------------\r\n\r\nThese FoxPro 2.5b help file topics contain the following\r\nline:\r\n\r\n\"Note that MODIFY STRUCTURE also marks a table with the\r\ncurrent code page.\" \r\n\r\nThis line is incorrect and should read:\r\n\r\n\"Note that MODIFY STRUCTURE doesn't mark a table with the\r\ncurrent code page. Rather, it preserves the table's \r\nexisting code page mark.\" \r\n\r\nInternational/X-Platform Topic\r\n------------------------------\r\n\r\nThis help file topic contains the following line:\r\n\r\nFor example, if the current collation sequence is GENERAL,\r\nboth of these return true (.T.):\r\n\r\n\t\"Straße\" = \"Strasse\"\r\n\r\n\tand\r\n\r\n\t\"Straße\" == \"Strasse\"\r\n\r\n\"Straße\" == \"Strasse\" will always return .F., not .T. as\r\nit states in this topic. A strict machine comparison is\r\nperformed by ==. All characters in each string are\r\ncompared, including trailing blanks. For more information\r\nabout comparisons using = and ==, see SET EXACT in the\r\nLanguage Reference or the FoxPro help facility.\r\n----------------------------------------------------------\r\n =================\r\n End of README.TXT\r\n =================" }