Try the Base today with the latest build. Many of the old bugs are gone. This is really good.
I have couple comments though.
Some bugs are still there. I know this is dev build, but I think the Base app seems to have unusual large number of obvious bugs (I mean with less than 5 minutes testing, I could find tons of bugs for every release I have tried so far, and some bug is like: cannot create a new database/this is fixed in this release though).
1) If you create a new table a number type and auto-increment, but not specify it as primary it, it will be primary key when save. Is this a desired behavior? When you create a table with auto-increment and nto specify any col as primary key, it will as for auto generate of primary key. If answer yes, you'll see error:
Attempt to define a second primary key in statement [CREATE TABLE "Table2" ("ID" INTEGER NOT NULL,"a" VARCHAR(50),"b" VARCHAR(50),"c" INTEGER IDENTITY, PRIMARY KEY ("ID")]
So, shouldn't it detect that "c" already a primary key, and not asking for the auto-creation of "ID"?
2) If connect to ODBC linking to .mdb file, queries and tables are both listed under table category. Is this desired?
3) When edit table definitions, as you change col's field type, different fields are show up. This is really funky to the eyes. I think a better design is to have them all show up and keep them in a same position. However, enable and disable them as you go. If there's more fields than space allow, use scroll bar (like in a table view). I don't think space is a constraint here.
4) Open a MS .mdb database linking through ODBC, I cannot edit a table def. Is this desired behavior?
5) The new database wizard does not remember my selection on register the database in open office.org. Actually, I am not sure what this is, and it should not be in this screen. It could go somewhere, but not here. I would rather keep it simple here.
6) New database wizard asks if open for editing. I think this should always be the case, and need not to be asked. Users can always close the window later. There's no need to give too many unneccessary option. I think by default, just open the "Base". On the file menu, user can choose to open the DB creation wizard. On the option menu, users can specify if this is shown when the the Base is run. If so, the base is started up and shown. Then the wizard is shown. For the file menu, there should be 2 create new database menu items: a) Create new database (this will be a hsqldb), no option other than file name is needed here. b) Connect to existing database. The purpose of this is to shorten the number of step to reach users' goal.
7) I Have the Base open in many windows. When click on it again to create a new database, it will not remember my previous directory where I open the file dialog (always go back to My Documents). By the way, this documents has some non-english in the bottom. This should be fixed.
8) Create a new database, check Create tables using the table wizard, but not check Open the database for editing. No table wizard was shown up. I am not sure what's to expect here, but I think there's something wrong with this wizard, and this is an example of it.
As you can see, I am not trying to nitpick here. I know it's dev release (again). However, it's so easy to pick and choose where I can point out a bug in this apps (with simple operations). This is something I think the developers need to think about. My suggestion is to look back at the way you develop your stuffs. Maybe more document, more design, more paper. Do more little tests as you go. If this is not fixed, I think majority of time will be fixing bugs which is very unproductive.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
