Liren Large Software Subsidy 7

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 7 / 07.iso / c / c150 / 1.ddi / README < prev next >

Wrap

Text File | 1990-12-10 | 74.5 KB | 2,372 lines

Db_Vista 3.20 README file 12/10/90. The following have been fixed for this release: ------------------------------------------------------------------ SCR NUMBER: 52 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DEVELOP DB_VISTA SET (BINARY) EDITOR DESCRIPTION: Develop a binary editor for correcting set pointers, record ID's and member counts, etc. ------------------------------------------------------------------ SCR NUMBER: 106 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CREATE UTILITY THAT CREATES COMPACT KEY FILE DESCRIPTION: Our key files maintain a fill level of just over 50%. This ability will create a new keyfile by first analyzing the existing keys and calculating ahead of time the number of nodes required. The nodes would be totally filled(for static records, or cd_rom) or minus one, for subsequent updating). This ability would create much smaller key files, hence faster access. ------------------------------------------------------------------ SCR NUMBER: 121 PRODUCT DB_VISTA 3.10 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ADD D_CURKEY CALL AFTER SCANNED KEYS IN IDA DESCRIPTION: When you use FIND and then NEXT, it works correctly. When you use SCAN, select a record and then NEXT, you get the next record after the last value on the scan list. This is not logical. Both FIND and SCAN followed by next should work the same way. ------------------------------------------------------------------ SCR NUMBER: 197 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCLEAR TO CLEAR OTHER ABORTED PROCESSES'S LOCKS DESCRIPTION: cleardb now only clears the downed stations locks( by using the the environment variable DBUSERID on that station.) A line option should allow you to specify another DBUSERID, without changing your own. ie CLEARDB wayne <RETURN> would clear waynes locks from any station.. If no user were specified, it would default to your own DBUSERID. ------------------------------------------------------------------ SCR NUMBER: 241 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: ADD CRGET AND CRSET EQUIVALENT FOR KEYS DESCRIPTION: Would be nice to have a CRGET() and CRSET() equivalent for keys. This is done with d_curkey function. ------------------------------------------------------------------ SCR NUMBER: 284 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: INCREMENTAL DATABASE OPEN / CLOSE ------------------------------------------------------------------ SCR NUMBER: 332 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DDLP DOES NOT CHECK THAT PATH LENGTH ARE LESS THEN 48 CHARACTERS DESCRIPTION: The runtime restricts path lengths to 48 characters. DDLP does not check to make sure the path names in the schema are < 48 characters. If path that is longer than 48 characters is supplied, sometimes ddlp completes successfully and sometimes it simply gives an "abnormal program termination" error. PRDBD shows the path contains garbage at the end. SOURCE FIXES: DDLP will now check the length of file names. ------------------------------------------------------------------ SCR NUMBER: 363 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: FILE SYNC FUNCTIONS DESCRIPTION: add a file sync function to replace dio_close / dio_open at d_trend. ------------------------------------------------------------------ SCR NUMBER: 380 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_open OS: Generic Unix STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: UNIX IPC NOT CLEANED UP AFTER GETTING -905 DESCRIPTION: If an open is attempted on an uninitialized database, a -905 error occurs. However, the message queue and semaphores (on Unix) have not been cleaned up and a cleardb must be run. WORK AROUND: ------------------------------------------------------------------ SCR NUMBER: 381 PRODUCT DB_VISTA 3.00 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: EXCLUSIVE OPEN SHOULDN'T REQUIRE PRESENCE OF FILES DESCRIPTION: the d_open(....,"x") call will fail if initdb has not been used. It returns a -905 error S_NOFILE. It needs to go ahead and allow the open, so that d_initialize and initfile can be used. ------------------------------------------------------------------ SCR NUMBER: 384 PRODUCT DB_VISTA 3.00 TYPE: Documentation Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: LIST OF FUNCTIONS REQUIRING READ AND/OR WRITE LOCKS AND WHEN. DESCRIPTION: Similar to table 7-4, users guide, List functions that require read locks and under what conditions. Also list functions that require write locks and under what conditions. ------------------------------------------------------------------ SCR NUMBER: 401 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_fillnew OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_FILLNEW WITH "LARGE" KEY GIVES STACK OVERFLOW ON DOS DESCRIPTION: d_fillnew will give a stack overflow if many records are added, and there are only a few slots per key page. For example, with a integer key array of 100 bytes, there are four slots per key page. The program can add 200 records and then gets a stack overflow error. If the integer key array is reduced to 40 bytes (hence 11 slots per key page), the program can add 6400 records before getting a stack overflow error. WORK AROUND: increase page size or decrease size of key. ------------------------------------------------------------------ SCR NUMBER: 402 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: PROVIDE KEYBUILD AS A FUNCTION. DESCRIPTION: allow customer to call keybuild as a function, This would allow them to provide their customers the ability to fix corrupt keys. ------------------------------------------------------------------ SCR NUMBER: 434 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_renfile OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: MEMORY LEFT UNFREED WHEN D_RENFILE IS USED. DESCRIPTION: When d_renfile is used there is a 10 byte memory block that is not freed. ------------------------------------------------------------------ SCR NUMBER: 467 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCHECK NEEDS TO OUTPUT MORE INFORMATION WHEN IT FINDS ERRORS DESCRIPTION: DBCHECK needs to output more information when it encounters errors in a database, to assist in debugging and or fixing a corrupted database. e.g. when scanning sets, output the dba of the owner when error is found in the set. Maybe also output dba of previous and/or next members as well. (when appropriate) ------------------------------------------------------------------ SCR NUMBER: 499 PRODUCT DB_VISTA 3.00 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ADD MULTITASKING CAPABILITY TO DB_VISTA FOR OS'S LIKE OS2 ETC. ------------------------------------------------------------------ SCR NUMBER: 509 PRODUCT DB_VISTA 3.00 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_OPEN DOES NOT CLEAN UP AFTER ITSELF IF IT FAILS. DESCRIPTION: if d_open fails the following sequence fails. d_dblog("/turkey"); d_open("tims","o"); -907 error (correct) d_dblog("vista"); -1 error, data base still open. ------------------------------------------------------------------ SCR NUMBER: 512 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: R_DELREC IGNORES RETURN CODES FROM DIO_WRITE. - CHECK OTHER DIO_WRITES DESCRIPTION: r_delrec ignores the return code from dio_write. It goes on to call dio_pzdel, which might not be safe if dio_write fails. Besides this can also cause multiple dberr messages to the application ie S_NOTRANS. In general, the runtime should not ignore return codes. ------------------------------------------------------------------ SCR NUMBER: 541 PRODUCT DB_VISTA 3.00 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_DISDEL DOES NOT PROPERLY SET CURRENT MEMBER DESCRIPTION: If d_disdel() is used on a record that owns a set the record is properly disconnected from the set it owns (i.e. - all its members are deleted) - but the current member is not set to NULL. As it is - the current member (in this case) is left undisturbed. Thus - the "current member" after disdel() is not owned by this set - but remains the sets "current member" - illogical.WORK AROUND: Do not rely on the current member for sets affected by d_disdel(). ------------------------------------------------------------------ SCR NUMBER: 544 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_open OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ALLOCATED MEMORY NOT BEING FREED DESCRIPTION: Some of the memory that is allocated during d_open is not being freed at d_close. This is often happens if the d_open fails. WORK AROUND: Try not to open and close the database often within one process. ------------------------------------------------------------------ SCR NUMBER: 552 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_connect OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: SETS ORDERED ASCENDING ON UNSIGNED FIELDS DO NOT WORK PROPERLY. DESCRIPTION: Ordered sets on unsigned fields do not work. The sign bit is not ignored. Hence 130 falls before 127 for an unsigned char sort by field. However, unsigned integers seem to work fine. ------------------------------------------------------------------ SCR NUMBER: 561 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: FUNCTION PROTOTYPES WHERE DBN IS ONLY PARAMETER. DESCRIPTION: When ANSI and LINT_ARGS are used the Microsoft C 5.1 compiler 'throws away' the prototypes where the DBN is the only parameter in dproto.h. Also, when compiling with -W3 d_disdel and d_delete prototypes give errors. ------------------------------------------------------------------ SCR NUMBER: 562 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: d_on_opt OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: REFERENCE MANUAL PAGE 113, USERS GUIDE PAGE 89 (SEE PROBLEM) DESCRIPTION: users guide, page 89, end of page change: d_on_opts(DBCHAINUSE | ARCLOGGING); d_off_opts(TRLOGGING | ARCLOGGING); to: d_on_opt(DCHAINUSE | ARCLOGGING); d_off_opt(TRLOGGING | ARCLOGGING); ------------------------------------------------------------------ SCR NUMBER: 568 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Consistency Check Utility (DBCHEC OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCHECK REPORTS ERRORS IN DELETED RECORDS WITH RLB SET. DESCRIPTION: When DBCHECK finds a record that had it's record lock bit set when it was deleted it reports it as an invalid record type. WORK AROUND: Try to clear lock bits before deleting the record or ignore the error message. ------------------------------------------------------------------ SCR NUMBER: 569 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Record Lock Bit Functions OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: RLB FUNCTIONS STATE OPTIONAL DBN CAN BE PASSED TO THEM DESCRIPTION: The reference manual says that the record lock bit functions take an optional database number. They do not in db_VISTA 3.10. They will in future releases. The bug is that the do not currently support the database number. ------------------------------------------------------------------ SCR NUMBER: 577 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Export Utility (DBEXP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBEXP DOESN'T EXPORT \R AND \N CORRECTLY. DESCRIPTION: If the ASCII values for cr or lf are encountered in a string they are exported as the ASCII values instead of "\r" or "\n". This causes records in the .txt files to be split onto multiple lines causing dbimp to crash. SOURCE FIXES: DBEXP will now format characters between '\000' and '\040', and above '\177' with a preceding escape character. It will use octal notation except for the standard codes for Carriage Return (\r), New Line (\n), Tab(\t), Form Feed (\f), and Backspace (\b). In addition, dbexp will export international characters (as defined in VISTA.CTB) as-is. Thus characters above '\177' which are defined as international characters will not be translated into octal codes. ------------------------------------------------------------------ SCR NUMBER: 581 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: NO NAME ON LOCK REQUEST STRUCTURE. DESCRIPTION: The LOCK_REQUEST typedef should have a struct tag name so that it can be prototyped correctly. WORK AROUND: Add a struct name ( lock_request ) to the LOCK_REQUEST typedef in vista.h ------------------------------------------------------------------ SCR NUMBER: 582 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: PROTO.H SYSTEM CALLS CONFLICT WITH MSC 5.1 DESCRIPTION: The prototypes for memcmp, memcpy and memset conflict the standard prototypes. This occurs for any source file which includes dbtype.h and memory.h. WORK AROUND: Change db_type.h to have memcpy to return a (void *) instead of an int. ------------------------------------------------------------------ SCR NUMBER: 583 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DAL CANNOT BE BUILT WITH NO_COUNTRY. DESCRIPTION: d_ctbpath is not defined when NO_COUNTRY is specified but DAL attempts to use it anyway. SOURCE FIXES: An #ifndef NO_COUNTRY has been placed around the declaration of d_ctbpath in dalmain.c. This allows it to compile if NO_COUNTRY is defined. ------------------------------------------------------------------ SCR NUMBER: 614 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: TURBO LINK WARNINGS, SLEEP IS IN VISTA LIB AS WELL AS IN TURBO LIB. ------------------------------------------------------------------ SCR NUMBER: 622 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: POINTERS TO CHARS IN DPROTO.H CAUSES WARNINGS. DESCRIPTION: Pointers required as parameters to db_VISTA functions are prototypes as (char *). For compilers that support ANSI these pointer should be (void *). WORK AROUND: If your compiler is ANSI compatible ( Microsoft, Borland, Lattice, etc ) edit the (char *) function parameters if dproto.h to (void *). ------------------------------------------------------------------ SCR NUMBER: 624 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_delete OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_DELETE ON RECORD WITH RLB SET CORRUPTS RECORD ID. DESCRIPTION: When a record which has it's record lock bit set is deleted it's record lock bit is not masked out. This causes DBCHECK to report the record as an invalid type. ------------------------------------------------------------------ SCR NUMBER: 629 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: COMPILING WITH NO_TRANS CAUSES ERRORS IN NETWDOS.C ------------------------------------------------------------------ SCR NUMBER: 630 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: COMPILING WITH WINDOWS AND FUNCTION PROTOTYPES DESCRIPTION: Some functions using DBN_D1 get preprocessed down to /**/ which causes compiler syntax errors. ------------------------------------------------------------------ SCR NUMBER: 632 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: MSC 5.1 ALIGNMENT PROBLEM. DESCRIPTION: With Microsoft C 5.1 there are some alignment problems. These are with arrays of structures. - DDLP will pad each element, MSC will not. WORK AROUND: Pad your structures to an even length yourself. ------------------------------------------------------------------ SCR NUMBER: 638 PRODUCT DB_VISTA 3.00 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_FILLNEW PRODUCING -17 FOLLOWED BY -901 ERRORS. DESCRIPTION: d_fillnew is not checking end condition of a loop correctly which causes -17 and -901 errors. ------------------------------------------------------------------ SCR NUMBER: 649 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_trend OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: OVERFLOW PAGES ARE LOST IF TRLOGGING TURNED OFF. DESCRIPTION: In d_trend() a section of code is skipped if TRLOGGING is turned off. A call to o_update() is not made, so any overflow pages are lost. The call should be made. ------------------------------------------------------------------ SCR NUMBER: 657 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_open OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: AFTER OPEN THE CURRENT RECORD IS NOT SET TO NULL. IF NO SYSTEM RECORD. DESCRIPTION: Maybe the current record should be initialize to null after the open call because if not crget will not return an error and the programmer may think the address is okay. ------------------------------------------------------------------ SCR NUMBER: 663 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Consistency Check Utility (DBCHEC OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCHECK.C: INCONSISTENT USE OF INT VS LOWER CASE INT DESCRIPTION: In dbcheck.c key_len and key_fld are declared as (INT *). When allocated with a call to calloc sizeof(int) is used. The call to calloc should use sizeof(INT). ------------------------------------------------------------------ SCR NUMBER: 680 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_fillnew OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: UNIQUE OPTIONAL KEYS ARE NOT ALWAYS UNIQUE DESCRIPTION: Multiple occurrences of unique optional keys are allowed to be added to the database. ------------------------------------------------------------------ SCR NUMBER: 685 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_close OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: GENERAL LOCKMGR DOESN'T REMOVE DBUSERID FROM DBL FILE IN ONE USER MODE DESCRIPTION: In one user mode the general lockmgr adds the DBUSERID to the dbl file when the database is opened but does not remove it when the database is closed. ------------------------------------------------------------------ SCR NUMBER: 687 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DDLP DOES NOT COMPILE WITH NO_FLOAT DEFINED. DESCRIPTION: DDLP does not compile correctly when NO_FLOAT is defined. SOURCE FIXES: In calc_align(), in file ddlalign.c, a divide by zero could occur in some cases. This was fixed by changing the following line: offset += ( (i - (offset % i)) % i ); to: if ( i ) offset += ( (i - (offset % i)) % i ); ------------------------------------------------------------------ SCR NUMBER: 692 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_setdb OS: OS/2 STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_SETDB DOESN'T WORK CORRECTLY. IN OS/2 DESCRIPTION: Using multiple databases. 1) if d_setdb is used then calls to d_setkey, d_fillnew, etc. return -4 errors. 2) if optional database parameters are used instead of d_setdb the application works ok. ------------------------------------------------------------------ SCR NUMBER: 704 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_crstat OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: D_CRSTAT, D_RECSTAT PRODUCE INVALID S_DELETED ERRORS. DESCRIPTION: If you open a database, d_fillnew a record then close the database. Then reopen the database, establish that record as your current record then call these functions they return S_DELETED. ------------------------------------------------------------------ SCR NUMBER: 706 PRODUCT DB_VISTA 3.10 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ADD OPTION THAT ALLOWS DBCHECK TO CLEAR RECORD LOCK BITS. DESCRIPTION: Add option to dbcheck that will cause it to clear any/all record lock bits that it found to be set. NEW UTILITY DBCLRLB ------------------------------------------------------------------ SCR NUMBER: 712 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Export Utility (DBEXP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBEXP CANNOT HANDLE LARGE FLOATING POINT NUMBERS. DESCRIPTION: dbexp would not process large numbers, exiting with an "unable to write to disk" message. SOURCE FIXES: The formatting of float and double data was performed with an sprintf into a fixed length string with a format string of "%f". This was changed to "%.20g" so that exponential notation will be used when the number is too large. ------------------------------------------------------------------ SCR NUMBER: 714 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_trabort OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: FREEING EXCLUSIVE LOCKS AFTER A D_TRABORT WRITES ABORTED CHANGES. DESCRIPTION: With the following procedure: 1) exclusive lock on file 2) make changes within transaction 3) abort transaction 4) free exclusive locks The freeing of the exclusive locks will flush some changes made in transaction. ------------------------------------------------------------------ SCR NUMBER: 719 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_setkey OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: MEMORY ALLOCATED USING D_SETKEY/D_MAKENEW NOT ALL BEING FREED. DESCRIPTION: Memory allocated with a d_makenew / d_setkey combination is not being freed. ------------------------------------------------------------------ SCR NUMBER: 720 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Interactive Database Access (IDA) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CANT ENTER A SINGLE BACKSLASH WHEN EDITING IN IDA. DESCRIPTION: IDA does not accept a single backslash "\" nor will it take "\\". ------------------------------------------------------------------ SCR NUMBER: 723 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_open OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: NETBIOS_CHK GENERATES FALSE POSITIVES. DESCRIPTION: The netbios_chk sometimes indicates that netbios is present when it is not. This happens when running with WINDOWS/386. ------------------------------------------------------------------ SCR NUMBER: 725 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_open OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: SHARED AND EXCLUSIVE MODES DO NOT WORK UNDER WIN386 WITH NBIOSE. DESCRIPTION: Under Windows/386 when running with Raima's netBIOS emulator shared and exclusive modes do not function correctly. They do if the computer is running on a network where the lockmgr is on a different node. WORK AROUND: Run on a network or use Windows/286. ------------------------------------------------------------------ SCR NUMBER: 730 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Interactive Database Access (IDA) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: EDITING DOESN'T WORK IN SOME CASES IN IDA DESCRIPTION: If you edit a record and you try to type over the existing structure or if you just try to move past it with the cursor keys the structure elements will be nulled out. ------------------------------------------------------------------ SCR NUMBER: 745 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_gtsco OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_GTSCO, D_GTSCR DO NOT WORK CORRECTLY. DESCRIPTION: The scenario is this: Open database. Create timestamped records. Close database. Open database. Set up currency. call d_gtsco, d_gtscr <-- looking at database shows ctime & utime = 2. functions return S_OKAY but Variable returned is set to 0, not 2. ------------------------------------------------------------------ SCR NUMBER: 761 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Consistency Check Utility (DBCHEC OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCHECK DOES NOT REPORT MISSING FILES. DESCRIPTION: When DBCHECK does not open a file no errors are reported and error count is not incremented. ------------------------------------------------------------------ SCR NUMBER: 763 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: IT IS POSSIBLE THAT DB_VISTA WILL NULL OUT DATABASE PAGES. DESCRIPTION: When db_VISTA attempts to read a page from a file and does not read the correct number of bytes, it assumes that we must need to add a new page. If the reason that the number of bytes returned from the file is a system error, db_VISTA will overwrite valid data with NULLs. ------------------------------------------------------------------ SCR NUMBER: 764 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_trend OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: THE TAF FILE IS NOT WRITTEN IF DOS MACHINE IS BOOTED DURING COMMIT. DESCRIPTION: The taf file is not written if DOS is booted or turned off during a commit. This is (probably) only true if the taf file resides on a local hard disk. ------------------------------------------------------------------ SCR NUMBER: 769 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_initialize OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_INITIALIZE FAILS WHEN DATABASE CONTAINS TOO MANY FILES. DESCRIPTION: The d_initialize function will run out of file handles if the database contains a large number of files. ------------------------------------------------------------------ SCR NUMBER: 771 PRODUCT DB_VISTA 3.10 TYPE: Enhancement REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: CHANGE FAR MACRO TO SOMETHING ELSE (DB_FAR, RFAR, ?) ------------------------------------------------------------------ SCR NUMBER: 773 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: COMPLETE THE "DUPLICATE FIELD NAME" CAPABILITY IN DDLP DESCRIPTION: Duplicate field names within structure don't work. Also, duplicate field names which are keys need to be disambiguated in key file and member... by statements. SOURCE FIXES: Ddlp will now accept a recname.fldname syntax in the "key file" statements. The same syntax may be used in "member...by" statements, but ddlp will use the record type named as the member. ------------------------------------------------------------------ SCR NUMBER: 803 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: WHEN FILE NAME EXCEEDS 8 CHAR DDLP DOES NOT CATCH DUP FILE NAMES DESCRIPTION: If the longer file name matches a shorter file name within the 8 char limit DDLP is not reporting the error, resulting in a corrupted database with the entry of a record into the conflicting file. Example: data file "dbpenf60.dat" contains ... data file "dbpenf602.dat" contains ... SOURCE FIXES: This has been fixed. When the root file name or the extension are longer than what is recognized by DOS, ddlp will produce a warning and shorten that component of the file name. ------------------------------------------------------------------ SCR NUMBER: 817 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DDLP SHOULD NOT ALLOW A RECURSIVE COMPOUND KEY DESCRIPTION: If a compound key uses its own name as part of the key DDLP generates a runtime error: divide by 0. SOURCE FIXES: A check is now performed so that a compound key cannot include itself in its definition. An error is generated. ------------------------------------------------------------------ SCR NUMBER: 820 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_setdb OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: UNDER WINDOWS D_SETDB AND MULTIPLE DATABASES DO NOT WORK DESCRIPTION: In db_VISTA 3.10 for WINDOWS d_setdb does not work correctly. ------------------------------------------------------------------ SCR NUMBER: 835 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: LOCK_REQUEST STRUCTURE PACKING/NOT PACKING DESCRIPTION: If you compile your code with MSC using the -Zp option for packing structures, in conjunction with using the -b option for DDLP then, the LOCK_REQUEST structure will generate a "invalid lock value" error when d_lock was called. This is due to the fact that db_VISTA is not compiled with the -Zp switch. WORK AROUND: If you have source you can recompile db_VISTA with a -Zp. You can also add a filler byte to the LOCK_REQUEST structure to get the correct alignment. You can use #pragma's to get even alignments around LOCK_REQUEST ------------------------------------------------------------------ SCR NUMBER: 840 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Interactive Database Access (IDA) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ENTRY OF UNSIGNED CHARS WITH IDA DOES NOT WORK DESCRIPTION: IDA not is representing unsigned chars correctly, nor is it writing them to disk correctly. ------------------------------------------------------------------ SCR NUMBER: 842 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ADD ADDITIONAL TEXT TO THE -917 ERROR. DESCRIPTION: The text to add is: This error will also happen on all other nodes using the database when the station running the lockmgr has been re-booted. The solution is to get all the other applications out of the database and restart the lockmgr and the allow the other applications to start up. ------------------------------------------------------------------ SCR NUMBER: 845 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_keyfind OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: COMPOUND KEY WITH FLOAT DESCENDING...KEYFIND WONT FIND DESCRIPTION: When a compound key has a floating point descending field d_keyfind will not locate the key correctly. SOURCE FIXES: This has been fixed in v3.15 for quite a while, but this SCR was never notified. The changes are on lines 99 and 104 of keyfind.c. On both lines, change fptr to tptr. ------------------------------------------------------------------ SCR NUMBER: 846 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: INCONSISTENT LOCKING REQUIREMENT IN TIMESTAMP FUNCTIONS DESCRIPTION: All but one of the timestamp functions require a lock. d_utscr does not require a lock. If this is safe then none should require a lock. All timestamp functions are now allowed without a lock. ------------------------------------------------------------------ SCR NUMBER: 860 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_reclast OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_RECLAST DOES NOT HAVE ONE_DB SUPPORT DESCRIPTION: The reclast source file will not compile correctly with ONE_DB set. ------------------------------------------------------------------ SCR NUMBER: 861 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: UTS IS A RESERVED WORD ON FUJITSU UTS/M COMPUTER ------------------------------------------------------------------ SCR NUMBER: 910 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_DELETE RETURNS S_INVADDR INSTEAD OF S_DELETED FOR A DELETED RECORD DESCRIPTION: When d_delete is called on a deleted record S_DELETED is not returned. ------------------------------------------------------------------ SCR NUMBER: 911 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_close OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBL FILE NOT CLOSED WITH A D_CLOSE WHEN DATABASE IN ONE USER MODE DESCRIPTION: When running with the general lockmgr in one user mode a call to d_close does not close the ".dbl" file. ------------------------------------------------------------------ SCR NUMBER: 918 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: LIST WHAT NEEDS TO BE LOCK TO USE EACH FUNCTION. DESCRIPTION: List what lock are needed to use a function (key, record, set etc. ). ------------------------------------------------------------------ SCR NUMBER: 921 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_fillnew OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_FILLNEW WITH MULTIPLE DATABASES AND LAST DB HAS NO KEYS GIVES ERROR DESCRIPTION: When a second database has no keys and the first database has keys a d_fillnew to a record in the second database will cause a "protection violation" in protected mode. WORK AROUND: Make the database with no keys the first database in the list of databases. ------------------------------------------------------------------ SCR NUMBER: 927 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_reclast OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: IF MORE THAN 1 DATABASE D_RECLAST RETURNS S_NOTFOUND FOR SECOND DB ON. DESCRIPTION: After opening multiple databases d_reclast will return S_OKAY only with database number 0. It returns S_NOTFOUND with all others. ------------------------------------------------------------------ SCR NUMBER: 928 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Database Session Clear Utility (CLEARDB) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CLEARDB SHOULD TAKE AN ARGUMENT FOR THE DBUSERID DESCRIPTION: CLEARDB should take the DBUSERID as a argument rather than only from the environment. ------------------------------------------------------------------ SCR NUMBER: 934 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_OPEN SHOULD NOT CREATE A .LOG FILE IF NOT TRLOGGING. DESCRIPTION: If trlogging is shut off with d_off_opt then no log files should be made. Now they are made whether needed or not. ------------------------------------------------------------------ SCR NUMBER: 951 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_recwrite OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DO CASE INSENSITIVE COMPARISONS WHEN DECIDING TO UPDATE RECORD. DESCRIPTION: db_VISTA compares the contents of the buffer passed to d_recwrite with the contents of the cache page. This comparison is done with the ignore_case option having an effect. As a result a data change with just a case change is ignored if ignore_case is on. ------------------------------------------------------------------ SCR NUMBER: 953 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: ALL STATUS: SCR is completed FIX IN VERSION: DB_VISTA 3.15 SUMMARY: DUPLICATE KEYS COULD BE CREATED WHEN UPDATING A RECORD. DESCRIPTION: When a record containing a structured key was updated a duplicate key could be added to a unique key. ------------------------------------------------------------------ SCR NUMBER: 956 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Lock Manager (LOCKMGR) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: GENERAL LOCKMGR AND DIFFERENT MEMORY MODELS DESCRIPTION: Then GENERAL LOCKMGR reads and writes pointers to the .dbl file. When different memory models are used this causes a problem. ------------------------------------------------------------------ SCR NUMBER: 964 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: PROTOTYPE OF FREE() IN "PROTO.H" DIFFERENT FROM ONE IN "STDLIB.H". DESCRIPTION: The Prototype of Free() in "proto.h" is "void Free (char*)" while MSC "stdlib.h" defines it as "void Free (void*)". ------------------------------------------------------------------ SCR NUMBER: 993 PRODUCT DB_VISTA 3.10 TYPE: Enhancement REFERENCE: Interactive Database Access (IDA) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: FROM SET SELECTION MENU, AUTOMATICALLY HIGHLIGHT LAST SET SELECTED. DESCRIPTION: This could be carried over to all list selections. ------------------------------------------------------------------ SCR NUMBER: 994 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: MULTIUSER VISTA IN ONE USER MODE NOT CLEARING CACHE. DESCRIPTION: Clear_cache() was failing to clear when multi-user version was opened in one-user mode. ------------------------------------------------------------------ SCR NUMBER: 995 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_fillnew OS: DOS-WINDOWS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DOING A D_FILLNEW() ON THE LAST RECORD OF DATABASE HANGS THE SYSTEM. DESCRIPTION: db_VISTA could check past the end of the field table when the last record of a database had no keys. ------------------------------------------------------------------ SCR NUMBER: 1011 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CHANGE SET NAMES IN INTERSECTION SET EXAMPLE, P. 64 DESCRIPTION: I've found it much more descriptive (and intuitively clear) to the novice (or the DBMS user) to use different names in the 2 sets in the example describing many-to-many and intersection set usage on pg. 64 of the manual. I rename the left set (presently "class-to-student") to "my-students" and rename the right set ("student-to-class") to "my-classes." ------------------------------------------------------------------ SCR NUMBER: 1012 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: d_setfiles OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DOCUMENTATION SAYS DEFAULT VALUE IS 5, SHOULD SAY 8. DESCRIPTION: The default for open files is set to 8. Should be reflected as such in documentation which says 5 on pg 180 of User's Guide. ------------------------------------------------------------------ SCR NUMBER: 1013 PRODUCT DB_VISTA 3.10 TYPE: Documentation Error REFERENCE: Interactive Database Access (IDA) OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CHAPTER 8 (IDA) OF THE USERS GUIDE NEEDS TO BE UPDATED DESCRIPTION: Chapter 8 of the user guide seems to be almost the same as the one for db_FILE. The menu descriptions do not match IDA for V3.10. ------------------------------------------------------------------ SCR NUMBER: 1014 PRODUCT DB_VISTA 3.10 TYPE: Enhancement REFERENCE: d_initialize OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_INITIALIZE SHOULD UTILIZE ARGUMENT "DBN" TO INITIALIZE 1 DATABASE. ------------------------------------------------------------------ SCR NUMBER: 1018 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: IF YOU COMPILE MU SOURCE WITH SINGLE-USER FLAG, IT DOES NOT WORK. DESCRIPTION: If n:SINGLE-USER is defined in config.vm, and you attempt to build the runtime library with the runtime n l command, the library will not be built. The solution is to put #ifndef SINGLE-USER at the beginning of the netwdos.c file and to place a #endif at the end. ------------------------------------------------------------------ SCR NUMBER: 1020 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: INCORRECT DDLP ERROR MESSAGE WHEN FIELD NAME = RECORD NAME DESCRIPTION: Summary: If a field name is the same name as the record it is contained in, the returned error is "non key field contained in key field". SCR Problem Text: Inappropriate error message returned from DDLP. ------------------------------------------------------------------ SCR NUMBER: 1021 PRODUCT DB_VISTA 3.10 TYPE: Software Error REFERENCE: d_delete OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_DELETE() AFFECTS CURRENCY OF OTHER DB'S IF MULTIPLE DATABASES USED. DESCRIPTION: If you open two databases and delete a record using d_delete in one of them, the currency in the other database will be changed if the same database address is a current owner or member. ------------------------------------------------------------------ SCR NUMBER: 1023 PRODUCT DB_VISTA 3.15 TYPE: Enhancement REFERENCE: OS: DOS-WINDOWS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: ENHANCEMENT FOR INCREMENTAL OPEN. DESCRIPTION: It would be nice to have some method of making Database numbers absolute, so that a particular database would always have the same number. As it is now with incremental opens, it can be anything. FIX: use new d_dbnum function. ------------------------------------------------------------------ SCR NUMBER: 1026 PRODUCT DB_VISTA 3.15 TYPE: Software Error REFERENCE: OS: DOS-WINDOWS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: WIDA3 OPENS BUT NEVER CLOSED/DISCARDS WIN87EM.DLL DESCRIPTION: Win87em gets opened; but the segments are not discardable, and it is not closed. ------------------------------------------------------------------ SCR NUMBER: 1027 PRODUCT DB_VISTA 3.15 TYPE: Software Error REFERENCE: d_crset OS: DOS-WINDOWS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_CRSET() IS NOT HANDLING ERRORS CORRECTLY. DESCRIPTION: Using TIMS database: 1. { x = -1; d_crset (&x);} =) unrecoverable error. 2. {d_encode_dba (&x,1,1000); d_crset (&x);} =) reports s_INVDBA but returns S_OKAY. ------------------------------------------------------------------ SCR NUMBER: 1029 PRODUCT db_VISTA 3.20 TYPE: Software Error REFERENCE: d_destroy OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_DESTROY RETURNS -49 S_INVPTR. DESCRIPTION: d_destroy works but always returns a -49 S_INVPTK if ONE_DB is not defined. Problem seems to stem from the following section of code from destoy.c: 1*free all residual memory*1 #ifndef ONE_DB termfree (-1_; NO_Of_dbs=D; #else termfree(); #endif ------------------------------------------------------------------ SCR NUMBER: 1030 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: INCORRECT -1 ERROR REPORTED BY DAL. DESCRIPTION: In dal, d_open returns a very misleading error code [may do it in runtime too]. If dbdpath is set correctly, but dbfpath does not point to the associated files, then when you enter "d_open ("tims","x");" you receive "error -1- database not open" and then "Database is unavailable" after you press <return>. (This does not happen in "O" or "S" mode. Is this because file opens are deferred until explicitly accessed, but in "X" mode they are immediately accessed in order to lock them?). In reality the files were not found which is what the error should be (-905), I think. ------------------------------------------------------------------ SCR NUMBER: 1031 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Documentation Error REFERENCE: Database Editing Utility OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: SIGNIFICANT ERRORS IN REFERENCE (PG 2-12) FOR DBEDIT DESCRIPTION: The manual describes commands (listed below) that are not implemented. Another command is different from the software: Commands apparently not implemented: fields, hex, nofields, source. NOTE: Manual says "show fld" works, but "show field" is required. Manual is consistent, software is inconsistent: display fld | show field. ------------------------------------------------------------------ SCR NUMBER: 1032 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DAL OR RUNTIME NOT DETECTING MISSING KEYFILE USING KEYFIND. DESCRIPTION: When using DAL, keyfind does not return an error message if (i) there is no key file present or (ii) you pass it a non-key field. e.g.: (using TIMS database in DAL) open ("tims","o"); [no data or key files present] keyfind (id_code,""); [no error (-905) produced] keyfind (goop,""); [no error (-17) produced]. note: 'goop' (in the above paragraph) should result in its own error code indicating "field/key referenced not found in data dictionary". ------------------------------------------------------------------ SCR NUMBER: 1033 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: TRANSACTION RECOVERY ERROR DESCRIPTION: With the MU library, if I compile and run a one-user application that adds data to and deletes data from 2 databases, then it does a debug check (d_txtest=1) and I hit return and re-boot while the hard disk light is on. Then I come in with IDA in one-user mode and recovery supposedly occurs (the message appears), but when I get out of IDA and run dbcheck, the database is corrupted. WORK AROUND: The bug was that db_VISTA was not clearing cache of static files in one_user mode. ------------------------------------------------------------------ SCR NUMBER: 1034 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: VMS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: READ MEMORY VIOLATION ERROR DESCRIPTION: READ MEMORY VIOLATION error happens in o_setup which calls alloc_table with a NULL pointer. Happens only on incremental opens in ports that support this error detection (e.g., VMS, Windows, OS/2). ------------------------------------------------------------------ SCR NUMBER: 1035 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: THE NEW "VAST" UTILITY DOES NOT DETECT THAT A FILE HAS ALREADY CHANGED DESCRIPTION: If VAST processes a file that it has previously processed, it corrupts the source code (it doesn't check to see if the file has already been modified to work with V 3.2). ------------------------------------------------------------------ SCR NUMBER: 1038 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Header Files OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: SCR 582 IS NOT FIXED. PROTO.H REDEFINITION ERRORS STILL OCCURRING DESCRIPTION: memcpy(), memset() and strlen() still get redefinition errors in PROTO.H. With both MSC 5.1 and 6.0 memory.h and string.h still have the three conflicts with proto.h. ------------------------------------------------------------------ SCR NUMBER: 1039 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Interactive Database Access (IDA) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: IDA DOES NOT DISPLAY BINARY DATA CORRECTLY DESCRIPTION: IDA does not properly display doubly subscripted char arrays. The last character is display as '/0' rather than its correct value. ------------------------------------------------------------------ SCR NUMBER: 1040 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_SETDB HAS PARAMETERS WRONG IN THE DOCUMENTATION DESCRIPTION: dt_setdb's parameters are reversed in dt_setdb in the reference manual. ------------------------------------------------------------------ SCR NUMBER: 1042 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_recfrst OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_RECFRST(????,-2) SHOULD RETURN -4 BUT INSTEAD RETURNS 0 (S_OKAY). ------------------------------------------------------------------ SCR NUMBER: 1043 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_recfrst OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: A BAD RECORD TYPE # PASSED TO DT_RECFRST DOES NOT RESULT IN AN ERROR DESCRIPTION: dt_recfrst was passed a record type number that was 1 greater than the last correct record type number. The return status was S_OKAY rather than -3, S_INVREC. ------------------------------------------------------------------ SCR NUMBER: 1044 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Database Session Clear Utility (CLEARDB) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CLEARDB WOULD NOT REMOVE LOCKMGR OR FREE MEMORY. DESCRIPTION: Neither "cleardb -l" nor "cleardb -a <name>" would remove a lock manager from operation and free memory. ------------------------------------------------------------------ SCR NUMBER: 1045 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DAL NOT DETECTING RUNTIME ERRORS DESCRIPTION: 1. DAL not detecting missing data or key files on d_open. 2. DAL not producing a -905 on d_keyfind when key file missing. 3. DAL not producing an error when a d_keyfind is performed on a field name not found in the data dictionary. ------------------------------------------------------------------ SCR NUMBER: 1046 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DAL NOT CORRECTLY PROCESSING ERROR UPON DATABASE OPEN. DESCRIPTION: In DAL, d_open returns a very misleading error code. If dbdpath is set correctly, but dbfpath does not point to the associated files, then "d_open("tims","x")" produces "error -1 - database not open" and then "Database is unavailable" after you press return. There is no message given if you open with "o" or "s" status (presumably since the actual file opens are delayed until an actual data request is made). In reality, the files were not found and the error message should reflect this fact. ------------------------------------------------------------------ SCR NUMBER: 1047 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Database Consistency Check Utility (DBCHEC OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBCHECK UNNECESSARILY INSISTS THAT ALL DATA & KEY FILES EXIST DESCRIPTION: Even when you want to check only one file, dbcheck insists that all files be present. This is an unnecessary restriction. (There are many cases where you may want to copy a file and test its integrity independently of the other files in the dictionary -- dbcheck should support this methodology.) ------------------------------------------------------------------ SCR NUMBER: 1048 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Database Consistency Check Utility (DBCHEC OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: RECORD #S ARE DISPLAYED IN A SHORT RATHER THAN AN UNSIGNED LONG DESCRIPTION: dbcheck appears to display record #s in a short - this is apparent when it prints numbers > 32767 as negative values. It should use an unsigned long instead. ------------------------------------------------------------------ SCR NUMBER: 1049 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DDLP DOES NOT CATCH DUPLICATE FIELD NAME ERRORS DESCRIPTION: ddlp does not detect some types of duplicate field names. The schema will compile without the -d option and indicate '0' errors found. Nor does it detect the reuse of a field name as a record, structure or set name. ------------------------------------------------------------------ SCR NUMBER: 1050 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: VMS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: MEMORY NOT BEING FREED DURING IOPEN AND ICLOSE PROCESSING-VMS SPECIFIC ------------------------------------------------------------------ SCR NUMBER: 1051 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Lock Manager (LOCKMGR) OS: VMS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: LOCKMGR CHANNEL NOT TERMINATED BY APPLICATION PROCESS ------------------------------------------------------------------ SCR NUMBER: 1052 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Runtime Library / DLL OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_DESTROY GIVES A -49 ERROR WHEN IT IS SUCCESSFUL ------------------------------------------------------------------ SCR NUMBER: 1053 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_recstat OS: STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_RECSTAT DOES NOT ACCEPT DBN. DESCRIPTION: The dbn parameter seems to be missing from d_recstat. ------------------------------------------------------------------ SCR NUMBER: 1055 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_setmo OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: SETMO GIVES A BAD RETURN CODE AND DB_STATUS UNDER CERTAIN CONDITIONS DESCRIPTION: A program lacking a setlock() call causes a -24 error for the setmo() function. However, the return code and db_status are trashed. ------------------------------------------------------------------ SCR NUMBER: 1056 PRODUCT DB_VISTA 3.15 TYPE: Software Error REFERENCE: OS: DOS-WINDOWS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: LMEMCMP SHOULD USE UNSIGNED COMPARISONS DESCRIPTION: In module lmemory.c function lmemcmp should declare buf1 and buf2 as: unsigned char DB_FAR*buf1; otherwise sign extension comparisons are performed. ------------------------------------------------------------------ SCR NUMBER: 1058 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_dblog OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_DBLOG DOESN'T CHECK FOR MAX PATH LENGTH DESCRIPTION: dt_dblog doesn't check for a max path length like dt_dbfpath. It should be consistent. dt_dbtaf -- same. dt_ctbpath -- returns 2 -35 errors in a row with long path names. ------------------------------------------------------------------ SCR NUMBER: 1059 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keyfree OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYFREE DOESN'T RETURN -5 WHEN PASSED BAD FIELD VALUE (1 OVER) ------------------------------------------------------------------ SCR NUMBER: 1060 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keylock OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYLOCK DOESN'T RETURN -5 WHEN PASSED A BAD FIELD VALUE (1 OVER) ------------------------------------------------------------------ SCR NUMBER: 1061 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_reclock OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_RECLOCK FAILS TO RETURN -3 ERROR WHEN PASSED BAD REC VALUE (1 OVER) ------------------------------------------------------------------ SCR NUMBER: 1062 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_setlock OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_SETLOCK DOESN'T RETURN -2 WHEN PASSED BAD SET VALUE (1 OVER) ------------------------------------------------------------------ SCR NUMBER: 1063 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Data File Dump Utility (DATDUMP) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DATDUMP GIVES NO DIAGNOSTICS IF INVALID OPTIONS SUPPLIED DESCRIPTION: Also, some options seem mutually exclusive, but the manual specifies using both and no error is produced. ------------------------------------------------------------------ SCR NUMBER: 1064 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Database Session Clear Utility (CLEARDB) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CLEARDB WON'T ACCEPT -A AND -U OPTIONS. DESCRIPTION: It also does not produce any diagnostic messages if bad arguments are given -- it just displays the usage message. ------------------------------------------------------------------ SCR NUMBER: 1065 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Database Editing Utility OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DBEDIT SHOW FIELD COMMAND DOESN'T SUPPORT DUPLICATE FIELD NAMES DESCRIPTION: dbedit displays the definition for the 1st duplicate field found in the .dbd file. Cannot enter RECORD_FIELD or RECORD.FIELD. The "display fld" doesn't work either. The command accepts the "fld" name, but gives a "Field is not in current record" error. ------------------------------------------------------------------ SCR NUMBER: 1066 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: db_VISTA Access Language (DAL) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: CRREAD AND CRWRITE DO NOTHING -- DON'T EVEN COMPLAIN ABOUT BAD PARMS ------------------------------------------------------------------ SCR NUMBER: 1067 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DDLP -D DUPLICATE FIELD NAME CHECKING IS INCOMPLETE -- ILLEGAL DUPS DESCRIPTION: DDLP -d does not accurately detect the following duplicate names: 1. Structures in different records with same name. 2. Name of structure the same as the name of field in same record. 3. Name of element in structure same as name of field in same record. 4. Set name same as record name. ------------------------------------------------------------------ SCR NUMBER: 1068 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Data Definition Language Processor (DDLP) OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: NO USAGE INFO DISPLAYED WHEN DDLP ENTERED WITHOUT ARGUMENTS ------------------------------------------------------------------ SCR NUMBER: 1070 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_setkey OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_SETKEY DOESN'T RETURN -5 WHEN FIELD=6000L (5000L LAST VALID) ------------------------------------------------------------------ SCR NUMBER: 1071 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keyfree OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYFRST DOESN'T RETURN -5 WHEN FIELD = 6000L (5000L LAST VALID) ------------------------------------------------------------------ SCR NUMBER: 1072 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keyfind OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYFIND DOESN'T RETURN -5 ON BAD FIELD # ------------------------------------------------------------------ SCR NUMBER: 1073 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keynext OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYNEXT DOESN'T GIVE -5 WHEN BAD FIELD # USED ------------------------------------------------------------------ SCR NUMBER: 1074 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_keyprev OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_KEYPREV DOESN'T GIVE -5 WHEN BAD FIELD # USED ------------------------------------------------------------------ SCR NUMBER: 1075 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: Generic Unix STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: UTILITY/FILEIO.C SHOULD NOT INCLUDE SYS/STAT.H. DESCRIPTION: Utility/fileio.c includes both dbtype.h and sys/stat.h, but sys/stat.h is included in dbtype.h. ------------------------------------------------------------------ SCR NUMBER: 1076 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_trabort OS: SUN STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_TRABORT CAN CAUSE CORRUPTION FOR TRANSACTIONS WITH STATIC FILES DESCRIPTION: If a transaction is aborted in one-user mode with the normal multi-user library, set corruption will occur. This is with the CLOSEFILES option on or off--it makes no difference. ------------------------------------------------------------------ SCR NUMBER: 1077 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: SHOULD NOT USE DB_VOID TO PROTOTYPE FUNCTIONS DESCRIPTION: For compilers that do not support void pointers (e.g., Ultrix), changing DB_VOID from void to char works fine except where DB_VOID is used as the function type. ------------------------------------------------------------------ SCR NUMBER: 1078 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: TASK.H GIVES INCORRECT #DEFINE FOR D_KEYREAD DESCRIPTION: In TASK.H, d_keyread() is incorrectly defined to require the use of a dbn parameter. ------------------------------------------------------------------ SCR NUMBER: 1079 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: TASK.H INCORRECTLY DEFINES D_RERDCURR() DESCRIPTION: TASK.H defines d_rerdcurr(a,b,CURRTASK), which should instead be d_rerdcurr(a,CURRTASK). ------------------------------------------------------------------ SCR NUMBER: 1080 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: Header Files OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: D_MAPCHAR & D_CTBPATH DEFINITION IS INCONSISTENT DESCRIPTION: TASK.H #defines d_mapchar(-) and d_ctbpath(-), but doesn't define dt_mapchar() or dt_ctbpath(). ------------------------------------------------------------------ SCR NUMBER: 1081 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: MS/PC-DOS STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: IN VAST.EXE USE OF D_KEYREAD DOES NOT SET CURR_DB. ------------------------------------------------------------------ SCR NUMBER: 1082 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: FREE ERROR IN RWCURR.C DESCRIPTION: Error in RWCURR.C for function WRCURR. It was not freeing memory correctly. Should be free(&currbuff) instead of free(curbuff). ------------------------------------------------------------------ SCR NUMBER: 1083 PRODUCT db_VISTA 3.20 BETA 1 TYPE: Software Error REFERENCE: d_lock OS: ALL STATUS: SCR is completed FIX IN VERSION: db_VISTA 3.20 SUMMARY: DT_LOCK DOES NOT WORK ON A SECOND DATABASE DESCRIPTION: If a lock is attempted on a second database, a -3 error (invalid record) is returned.