Hard to find the best solution here.

I agree that the tristate is potentially confusing for unexperienced
users, but I wouldn't argue that it's completely nonsense to set it to
this state even in an existing record which was initialized before.
This feature may be desirable for experienced users.

Customizing this (on a per-table basis) may be a good solution.

Another way: an extension of the table design: Currently, the table
design does not distinguish between server-side ("server" in a more
general sense, so that we also include our dBase implementation)
properties and client-side properties. Examples for such properties
would be:
- the type of a column - this clearly is something which is stored in
the database
- the control which is to be used to display a column
- the server-side default of a column, this can be some meta-data like
"USER", which would cause the database to automatically insert the
name of the current user when a new record is interted.
- the client-side default of a column, which is presented in the UI
when a new record is entered (in opposite to the server-side default).

Implementing a table design which distinguishs between the real table
structure as far as the server is concerned, and the client-side
representation of a column, would automaticall allow specifying
something like "this boolean column should be displayed with a
checkbox control which does not allow the 'intedermined' state".

At the moment, I'd prefer the last solution, though it's the most
extensive one. But perhaps there are other ideas, too :)

Hi,

Some additional thoughts from my perspective which may help.

The Text Box is fine with Tristate/Bistate fields as this can be set.

With the Table Control if I could right click on the heading and set 
the checkbox column to tristate or bistate and have this stick that 
would be good.

With the data source window if I could right click in the heading of 
a checkbox field and select tristate or bistate and have that stick 
to this data source that would be fine.  If the data source was 
deleted and created again I would expect to have to reset this.  To 
me this could work the same as the Column Format -> Alignment for a 
column in the data source.

So I'm not suggesting too much in the way of smarts.   Just the 
ability for the user to determine the settings.  Smarts are good, 
but I am more than happy just to be able to define these settings.

Hope that helps

Kelvin

Hi kelvine,

Does this problem still exist in “OOo 1.1.0�

If it does, please:
- attach a very small dbase database and a step by step instruction how to 
  reproduce your problem, so that it can be reproduced by anyone without any 
  knowledge in database access.
- find a better summary for this issue as an enhancement request like
  "OOo ... should have ... because ..."

If I will not see any further action as votes, attachments or confirmations in
this issue, I will have to close this issue 2004-01-31 as WFM.


CU

Rainer 

Hi,

As requested I will attach a dBase table called Issues.dbf.

Under Windows this file can be placed in the folder "C:\Program 
Files\OpenOffice.org1.1.0\user\database\biblio". That means it is available as 
part of the Biblio datasource and no extra work is required to define a new 
datasource.

Also attached is a Form/document which is called "Issue14970Form.sxw". This 
document can be run from anywhere. It links to the Issues.dbf table which is 
stored in the biblio folder as stated above.

The table has two fields
IssueNo: To hold the issue number
Resolved: A logical field which from a user perspective should be True or 
False.

Normally as a developer I would present the user with a Form. It would set the 
default value of Resolved to False.

The Form provided shows this behaviour.

Using the Form enter IssueNo=14790 and Resolved=False. That is unticked.

The checkbox on a form created using the Autopilot automatically sets up the 
checkbox field to Tristate=No and Default=Not Selected which is what we want.

OpenOffice.org provides a second method for the user to change the data. This 
is the datasource window.

For this example open Writer
Press F4 to open the datasource window
Click on the + in front of the Bibliography datasource
Click on the + in front of Tables
Click on the Issues table

At the right are the records that you have entered into the table.
For a record click on the checkbox for the Resolved column
Click again and then click again.

The checkbox cycles through three values.

Unticked -> Ticked -> Faint grey tick

These represent Selected, Not Selected and Not defined.

Using the Form we are able to set a default value (Not selected) and restrict 
Logical fields to Two values.

Using the datasource window it is not possible to set a default value and the 
user can force the field to a Not defined state.

The problems with this are:

- This could result in inconsistency of data
- Users being confused when expecting to only Select or Not Select the 
checkbox in the datasource window

This issue still exists in OOo1.1.0.

I hope this further information is of use.

Kelvin

Created attachment 12150 [details]
Issues.dbf table

Created attachment 12151 [details]
Simple data entry form showing checkbox

change subcomponent to 'none'

This Issue requires more information ('needmoreinfo'), but has not been updated
within the last year. Please re-test with one of the latest versions of OOo -
the problem(s) may already be addressed. Either use the latest stable version:
http://download.openoffice.org/index.html
or consider trying the new OOo 3 BETA (still in testing):
http://download.openoffice.org/3.0beta/

Please report back the outcome of your testing, so that this Issue may be closed
or progressed as necessary - otherwise the issue may be Resolved as Invalid in
the future.

Regards
Andrew

Cleaning-up and Closing old Issues as part of:
~ The Grand Bug Squash, pre v3 ~

no response -< invalid

-> closed