Dear SCO Customer, Support Level Supplement (SLS) APP336C for SCO FoxBASE+ Runtime System Release 2.1.2 and/or SCO FoxBASE+ Development System Release 2.1.2 contains the year 2000 modifications and other minor fixes. SLS APP336C supersedes SLS APP336B and, if installed, SLS APP336B should be removed prior to installing SLS APP336C. The documentation for the fixes from the previous version of this SLS are included here for convenience. Previous versions of this SLS are no longer available. SLS APP336C can only be obtained from SCO's Web site (www.sco.com) or from SCO's ftp site (ftp.sco.com). IMPORTANT NOTE: It is strongly recommended that you also install SLS UOD426C, the year 2000 patch for the operating system utilities. However, the installation of SLS UOD426C (or fix2000) has no effect on this version of SCO FoxBASE+, or any applications running under SCO FoxBASE+. MAJOR CHANGES INCLUDED IN SLS APP336C ------------------------------------- 1. New Year 2000 Modifications A. The date() function has been modified to accommodate dates past the 20th century. B. There is a new shell environment variable FOXYEAR that is recognized by FoxBASE+. C. The new command "set foxyear to " has been added. Internally, FoxBASE+ stores year numbers as 4 digit years. However, unless "SET CENTURY" is set to "ON", the year portion of the date is only displayed, or able to be entered, as a two digit number. As a two digit year number, this defaulted to the 20th century (1900-1999) when entered at the keyboard or in an application that inserted a date as a two digit year using any of the date functions. The FOXYEAR environment variable may be used to change this behavior globally for all applications on a per user or per system basis, or the "SET FOXYEAR TO " can be used within applications to change this behavior programmatically. If neither of these commands are used, FoxBASE+ reverts to its original behavior (20th century). NOTE: Simply installing this SLS does not resolve the year 2000 limitation presented in the original FoxBASE+ product. You must specifically set FOXYEAR to the appropriate value for your application(s). Users should contact their software vendor before applying this SLS. The specified to either of these constructs implements a 100 year sliding window. Any two digit years that fall within this 100 year window will default to the century on or before . This affects date calculations and conversions, as well as enterable data that represent the year as two digits. When is set to anything above 1999, two digit dates may default to the 21st century or above. You may also use this feature to incorporate default centuries for the previous two centuries (the 18th and 19th centuries). However, FoxBASE+ officially does not support, in any format, years before 1751 (for historical reasons). To demonstrate, if is set to 2084, years entered as two digits between 85 and 99 (inclusive) will be considered to be 1985 to 1999; years entered as 00-84 will be considered to be 2000-2084. 2084 is the recommended setting for most applications that do not store dates before the application was implemented. If you had ported an application from dBase II or earlier, you may need to set the slightly earlier. If your application stores historical data from many centuries, it is recommended that you "SET CENTURY ON", change the programmatically using "SET FOXYEAR", as applicable, or simply using another datatype other than type "Date". An example follows: If FOXYEAR were set to 2050, for example, the following date conversions would be performed: . SET FOXYEAR TO 2050 . ? YEAR(CTOD("01/01/00")) 2000 . ? YEAR(CTOD("01/01/49")) 2049 . ? YEAR(CTOD("01/01/50")) 2050 . ? YEAR(CTOD("01/01/51")) 1951 . ? YEAR(CTOD("01/01/99")) 1999 To make a global change to the whole system running FoxBASE+, add the line: FOXYEAR=;export FOXYEAR into the /usr/bin/foxplus and /usr/bin/foxprun shell scripts, or in /etc/profile (C-Shell users should add "set FOXYEAR=" in ~/.cshrc). To make the change effective only for certain users of a system, insert the above line into each user's ~/.profile. NOTE: FOXYEAR and "SET FOXYEAR" are not included in HELP, HELP SET, SYS(2001), SET, OR DISPLAY STATUS commands. Also, the construct "FOXYEAR=" is not valid in any config.fx file. 2. The screen is now cleared completely before append, change, help, modify report/structure/label, browse, insert, and set commands. 3. Erroneous "alias not found" messages were reported in unusual circumstances. 4. Core dumps in help screens or at the dot prompt when [CTRL]-P was followed by carriage return. 5. Support for 50 characters in menu items (previously 49). 6. New SYS(77) function returns the number of "names" (variables) slots left to the system. This starts at 2048 and works its way downward as names are declared. The number of variable assignments remains at 3,600 which includes array elements using the same "name". 7. ZAPped files remain open exclusively in all cases. UPGRADING TO SCO FoxBASE+ 2.1.2 ------------------------------- Users must first upgrade to SCO FoxBASE+ Release 2.1.2 before installing SLS APP336C. If any release other than SCO FoxBASE+ Release 2.1.2 is installed, SLS APP336C will fail to install. Contact your SCO software supplier to inquire about upgrading. You will need the serial number and activation key found on the pink card provided with the SCO FoxBASE+ Runtime System and SCO FoxBASE+ Development System. This information may also be found on the Certificate of License and Authenticity card provided with your SCO product. IMPORTANT NOTE: SLS APP336C supersedes SLS APP336 and APP336B. If SLS APP336B or APP336 is installed, remove them prior to installing SLS APP336C. INSTALLING SLS APP336C ---------------------- Note: If you have installed this SLS before, issue the command: # rm /etc/perms/foxsls+ This will remove any past reference to the SLS. 1. Download the SLS APP336C to an SCO UNIX System V/386 machine, making sure you specify a binary file transfer, if needed. The checksum/size of the app336c file should be: # sum -r app336c 17719 2880 app336c 2. Copy the SLS to a floppy diskette using the 'dd' command. On most systems this can be accomplished with the command: dd if=app336c of=/dev/install bs=18k The "of=/dev/install" should be your default floppy device, otherwise insert the correct device node for your system. Examples for a 3.5 inch floppy would be /dev/rfd0135ds18 or /dev/rfd1135ds18. (At this point, a sum -r on /dev/install or /dev/rfd0135ds18 should also match the sum mentioned above.) 3. Install the SLS using "custom". If you are using the second floppy device, you may need to use: custom -m /dev/rfd1135ds18 4. Select to install the "Entire Product" and follow the instructions on the screen. Use your "Activation Key" card that you received with your original purchase of FoxBASE+ Runtime and/or Development System versions to brand and enable the new versions of the FoxBASE+ binaries to be executed. 5. Installation of SLS APP336C is now complete. FIXES INCLUDED IN SLS APP336B AND APP336C ----------------------------------------- 1. When indexed data in a record is changed by another user, the SKIP() function will now behave in a predictable way. 2. Stored variables will be treated the same way in compiled and non-compiled programs. 3. Users will be notified if an EXCLUSIVE OPEN fails. 4. The default umask has been changed to 000. As a result, all database files will have read/write permissions for all users. This insures that indexing, packing, and sorting will not change user access to the database files. An individual user can override the SCO FoxBASE+ default umask with the system umask by invoking SCO FoxBASE+ with the following command: foxplus -u 5. The SYS(2000,"*prg") has been corrected to eliminate an error condition which would confuse standard in and standard out. The SYS(2000, "*.prg") will now return just the filename rather than the complete pathname. 6. CLOSE ALL, followed by CLEAR PROGRAM no longer causes SCO FoxBASE+ 2.1.2 to exit. 7. The MENU BAR command allows a menu array to contain 50 elements. 8. The SELECT 0 command behaves properly when used in conjunction with the ALIAS command. 9. The DISKSPACE() function returns the correct value for the remaining disk space. 10. Users will get the error message "File access denied" when they try to lock a database exclusively without write permissions on the database file. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier. We appreciate your business. SCO Support Services