Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!aramis.rutgers.edu!paul.rutgers.edu!yes.rutgers.edu!emuleomo From: emuleomo@yes.rutgers.edu (Emuleomo) Newsgroups: comp.databases Subject: Re: dBASE IV Problems Message-ID: Date: 7 Sep 89 09:14:20 GMT References: <205@cerc.wvu.wvnet.edu.edu> <3520010@hpindda.HP.COM> <208@dbase.UUCP> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 55 Path: paul.rutgers.edu!aramis.rutgers.edu!rutgers!cs.utexas.edu!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!awd Newsgroups: comp.databases Subject: Re: dBASE IV Problems Summary: Me again. Date: 6 Sep 89 17:22:49 GMT References: <205@cerc.wvu.wvnet.edu.edu> <3520010@hpindda.HP.COM> Organization: Ashton Tate Devlopment Center Glendale, Calif. Lines: 48 In article <208@dbase.UUCP> (Alastair Dallas) writes: >You need to provide a simple failing test case, however, if you expect >action. Do this and this to data like this and it fails, see? Sweeping >statements like "I lose data all the time that I'm sure was entered >correctly" may make you feel better, but I can't help you and in the >current Ashton-Tate-bashing atmosphere you're just adding fuel to the fire, >inviting people to make wild claims like "FoxBase never crashes" >(Try pasting a MacVision grayscale image into a memo in FoxBase/Mac and >watch it eat your hard disk before it dies--the hard disk errors are >recoverable, but the entire .dbf is lost.) Thanx for pointing out that bug. I will check it out on my mac!! Seems that you guys over at A-T are now using FoxBase/Mac instead of dBASE/Mac Looks like a good move to me. I also thimk that is a good endorsement of the product. If you ask me, that is what A-T should have produced in the 1st place. BTW, are you guys using Fox 2.1 yet? If so, please post any bugs you come across. I can't seem to find any! Although FoxBase is an excellent product, I'm sure it's not perfect. Only Wordperfect makes that claim. They even changed their name to Word Perfect Corporation!! > Since I am sure that v 1.1 of dBase IV has had a change freeze for > many a month now, I guess I can only WAIT and HOPE for improvements in > v 1.1. I would like to see, however, some acknowledgement by A-T that > these problems exist and are being considered by A-T. > > Regards No, actually, we're doing things differently these days. I probably can't go into it in any detail, but we're experimenting with different software methodologies that let a lot of asynchronous tasks be done in parallel--the notion of a "change freeze" is history, for example. 1.1 will be done when it's done--it won't be shipped on any arbitrary schedule. As I said last time, tell me exactly what to do to make dBASE IV crash, and I can practically guarantee you that we'll hold 1.1 until the problem is fixed. But how can you ask for acknowledgement that these problems exist without explaining them so that we can see for ourselves? /alastair/ Disclaimer: My opinions only, as usual. -- ** Research is what I'm doing when I dont know what I'm doing! **