apn@nonvon.UUCP (03/15/87)
Seeking recommendations for books on dbaseIII+ programming. Is
there anything comprehensive around ? I'm looking to avoid those books
in particular that have a low information content. ( like PCDOS manuals,
for example )
Thank you,
Alex P Novickis
--
UUCP: {sun, seismo, amdahl, lll-crg, 'etc'}!ptsfa!nonvon!apn
{* Only those who attempt the absurd ... will achieve the impossible *}
{* I think... I think it's in my basement... Let me go upstairs and check. *}
{* -escher *}regoli@silver.bacs.indiana.edu (michael regoli) (03/20/88)
In article <vu0112@bingvaxu.cc.binghamton.edu> (Cliff Joslyn) writes: -In article <bill@wsccs.UUCP> (Bill Housley) writes: ->Once I did the famous DBaseIII-editor-file to big-fry ->your fat-#@$^&*#$ mistake and spent 4 hours finding a disk utility that ->would help me re-construct it. - -Uh, could you *please* tell us what this was again? yes, please elaborate on this problem! how does it happen? and, while on the subject of dbase, can someone tell me about the maximum record size for a .dbf file? i heard after 2,500 records, an indexed database file it begins to act flaky... -- michael regoli regoli@silver.bacs.indiana.edu ...ihnp4!iuvax!silver!regoli
karl@ddsw1.UUCP (Karl Denninger) (03/21/88)
In article <1218@silver.bacs.indiana.edu> regoli@silver.UUCP (michael regoli) writes: >In article <vu0112@bingvaxu.cc.binghamton.edu> (Cliff Joslyn) writes: >-In article <bill@wsccs.UUCP> (Bill Housley) writes: >->Once I did the famous DBaseIII-editor-file to big-fry >->your fat-#@$^&*#$ mistake and spent 4 hours finding a disk utility that >->would help me re-construct it. >- >-Uh, could you *please* tell us what this was again? > >yes, please elaborate on this problem! how does it happen? > >and, while on the subject of dbase, can someone tell me about the >maximum record size for a .dbf file? i heard after 2,500 records, >an indexed database file it begins to act flaky... >...ihnp4!iuvax!silver!regoli I don't know about the FAT killer, but I do know about wierd index file problems and dBase III. Seems as though your index expressions should be an exact multiple of 4 bytes. Never did figure out exactly what the failure mode was, but things got really wierd if we violated this assumption. We saw problems way before 2500 records, though -- like immediately. Then again, our products do some rather "interesting" things with index files :-) Right now we have 3500+ records in a couple of dBase III databases (on clipper and foxbase) and see no trouble at all... Both the Clipper and Foxbase + do not exhibit the 4-byte anomoly (guess what we do our development under now :-). ---- Karl Denninger | Data: +1 312 566-8912 Macro Computer Solutions, Inc. | Voice: +1 312 566-8910 ...ihnp4!ddsw1!karl | "Quality solutions for work or play"
cline@pnet01.cts.com (Ben Humphreys) (03/26/88)
dBASE supports 1 billion records. To my knowledge dBASE does not get 'flaky'
around 2500 records. Clipper on the other hand has problems around 64k limits
when indexes are open in rare instances.
UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!cline
ARPA: crash!pnet01!cline@nosc.mil
INET: cline@pnet01.CTS.COMkarl@ddsw1.UUCP (Karl Denninger) (03/27/88)
In article <2731@crash.cts.com> cline@pnet01.cts.com (Ben Humphreys) writes: >dBASE supports 1 billion records. To my knowledge dBASE does not get 'flaky' >around 2500 records. Clipper on the other hand has problems around 64k limits >when indexes are open in rare instances. We use the Autumn '86 version of the Clipper and have seen no problems of this kind; we have some 700K+ .DBF and .NTX files around... ---- Karl Denninger | Data: +1 312 566-8912 Macro Computer Solutions, Inc. | Voice: +1 312 566-8910 ...ihnp4!ddsw1!karl | "Quality solutions for work or play"
leonard@bucket.UUCP (Leonard Erickson) (03/31/88)
In article <2731@crash.cts.com> cline@pnet01.cts.com (Ben Humphreys) writes:
<dBASE supports 1 billion records. To my knowledge dBASE does not get 'flaky'
<around 2500 records. Clipper on the other hand has problems around 64k limits
<when indexes are open in rare instances.
dBase III indexes can start acting extremely weird at as few as 1400 records.
I once was called in on a problem where they'd been using SET UNIQUE ON and
then indexing on a multi-field key to eliminate duplicate records. On day the
program went nuts. out of 1400-1500 records it came up with 20 in the index.
And watching it index was shocking too. It got up to 47% indexed and then there
was a *long* pause. Then it continued indexing.... all the way to 573%!!!!
It was indeed a bug in indexing. Ashton-Tate even admitted it to us. The "cure"
was dBase III+.
I've run into a different bug on DBII+. We've got a 100+ *thousand* record
file. It takes up over 15 meg. Both COPY TO and APPEND FROM with a FOR
sometimes fail to retrieve any records, yet the records are there. Going to
a record somewhat before the records being sought and repeating the SAME
command with a NEXT xxxx works. I'd love to know what is going on. The file
isn't indexed, it *is* in chronological order and the records are being
retrieved based on a date range.
--
Leonard Erickson ...!tektronix!reed!percival!bucket!leonard
CIS: [70465,203]
"I used to be a hacker. Now I'm a 'microcomputer specialist'.
You know... I'd rather be a hacker."wwang@ucscb.UCSC.EDU (Weylan Wang) (06/06/89)
Netlanders, My father has Dbase III+. He has an EGA monitor and he was complaining that he can't display 43 lines on the screen by default every time the machine is started up. I can go into the SET commands and find where to select the 43 line mode for the monitor, but try as I might, I could not figure out how to get the machine to start up in this mode. I know there must be a command to have it start in this mode by default. I chould hack it, but I just can't seem to find the right answer. The 43 line setting are in the second menu of the set commands. Any one know what command I should set in config.db to have it start in 43 line mode? Any help would be greatly apreciated. I could not look at the manual, because I am here at school. When I did see the problem, I did not have time to look in the book, but the on line help did not have anything useful to say. HELP!!!
awd@dbase.UUCP (Alastair Dallas) (06/14/89)
I checked the III+ manual, and I can't find a config.db command which sets up EGA 43-line mode (I can't recall one, either). Your father may be out of luck. dBASE IV, on the other hand, supports: DISPLAY = EGA43 in the config.db file. /alastair/