Base Field Defaut Disables Save

users
#1

Just begun working with Base, 3.3.2. Cannot set default field values because the Save function stops working if you add a value to any "default" field. When you add a default value, the Save icon is "enabled" but clicking has no effect. The icon remains enabled. And you can't close the edit window because you can't save changes.

Deleting the default value allows you to save. Other changes did not trigger the problem. The default values were valid. I tried many variations and I am quite certain some, at least, were perfectly valid entries.

Can anyone replicate this?

Cheers,
                tod

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#2

Tod

Just begun working with Base, 3.3.2. Cannot set default field values because the Save function stops working if you add a value to any "default" field. When you add a default value, the Save icon is "enabled" but clicking has no effect. The icon remains enabled. And you can't close the edit window because you can't save changes.

Deleting the default value allows you to save. Other changes did not trigger the problem. The default values were valid. I tried many variations and I am quite certain some, at least, were perfectly valid entries.

Can anyone replicate this?

Cheers,
                tod

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

Please advise your OS.

What type of field was causing the problem?

#3

Hi Tod,

Just begun working with Base, 3.3.2. Cannot set default field values because the Save function stops working if you add a value to any "default" field. When you add a default value, the Save icon is "enabled" but clicking has no effect. The icon remains enabled. And you can't close the edit window because you can't save changes.

Deleting the default value allows you to save. Other changes did not trigger the problem. The default values were valid. I tried many variations and I am quite certain some, at least, were perfectly valid entries.

Can anyone replicate this?

Hmmm, I can't remember whether I was able to set default values before
with OOo or not : did you use OOo previously, and if so, did it work
then, and with which version ?

I seem to recall that there were issues with setting default values in
OOo 3.2.x, but I can't remember whether these were addressed in the
3.3.x development (which corresponds mainly to current LibO versions).

Also, I assume you are referring to a native HSQLDB database, and not
trying to set defaults via some connector (ODBC/JDBC/MySQL) to an
external db server instance ?

Alex

#4

Sorry. I need to set up a config signature:

Mac OSX 10.6.7. Libreoffice 3.3.2 (brand new install). NeoOffice is also running on this machine.

Database is brand new, first use. Was just beginning to test Base which I have not used previously and ran into this problem setting up a table. Select edit table and enter "default" value parameter for any field. I tested several values for several fields and types. Any entry caused this problem.

Cheers,
                tod

Tod

Just begun working with Base, 3.3.2. Cannot set default field values because the Save function stops working if you add a value to any "default" field. When you add a default value, the Save icon is "enabled" but clicking has no effect. The icon remains enabled. And you can't close the edit window because you can't save changes.

Deleting the default value allows you to save. Other changes did not trigger the problem. The default values were valid. I tried many variations and I am quite certain some, at least, were perfectly valid entries.

Can anyone replicate this?

Cheers,
               tod

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

Please advise your OS.

What type of field was causing the problem?
--
Jay Lozier
Jslozier@gmail.com

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#5

Just occurred to me that I should attempt the same thing in NeoOffice which is a slightly earlier ver (3.1.2).

NeoOffice, let me click save and exit, but the changes to the "defaults" did not save. When I reopen in LO or NO, they are not saved.

I also realized that I WAS able to save defaults for the text based fields (Memo and Varchar) but not for Integer, Date, or Numeric fields. I said I couldn't save for any of the fields I tried.

Tod

Hi Tod,

Just begun working with Base, 3.3.2. Cannot set default field values because the Save function stops working if you add a value to any "default" field. When you add a default value, the Save icon is "enabled" but clicking has no effect. The icon remains enabled. And you can't close the edit window because you can't save changes.

Deleting the default value allows you to save. Other changes did not trigger the problem. The default values were valid. I tried many variations and I am quite certain some, at least, were perfectly valid entries.

Can anyone replicate this?

Hmmm, I can't remember whether I was able to set default values before
with OOo or not : did you use OOo previously, and if so, did it work
then, and with which version ?

I seem to recall that there were issues with setting default values in
OOo 3.2.x, but I can't remember whether these were addressed in the
3.3.x development (which corresponds mainly to current LibO versions).

Also, I assume you are referring to a native HSQLDB database, and not
trying to set defaults via some connector (ODBC/JDBC/MySQL) to an
external db server instance ?

Alex

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#6

I just tried to replicate this on Windows7 Professional. I was able to save
a table after setting a default text value in one field. However, after
that, I could not edit the the table structure at all. I could enter data in
the table but I could not alter the table by changing current field
properties, even if there was no data in the field.

#7

Try the solution suggested in this thread :

http://user.services.openoffice.org/en/forum/viewtopic.php?f=61&t=26194

i.e. Go to the Tools - SQL menu entry

Enter an ALTER table command to set the default value for each field as
you desire.

e.g. alter table T2 alter column C2 set default 0;

HTH,

Alex

#8

It appears that the UI default value setting capability available
through the table editor/designer is not propagated to the underlying
database by design, see this bug report :

http://openoffice.org/bugzilla/show_bug.cgi?id=108100

And it also appears that this will not be fixed any time soon, at least
not in the OOo code, given the work that would be required to fix it, so
it is probably even less likely to be done in the LibO code where there
are no specialist db developers AFAIK.

Currently, the only correct way to set a default value in the underlying
db is to issue a corresponding CREATE TABLE or ALTER TABLE statement via
the Tools - SQL menu entry.

Alex

#9

I would not have figured that out. The first thread suggests the preferred method for setting a default would be at the form level rather than at the table design level anyway. I will look to see if that can be done now. Makes sense to me.

I would very much like to use Base, but I'm at the edge of having sufficient knowledge to make it work. It appears that in order to make Base work for me, I will have to study MySQL and use it as my backend, with base as a front end.

Cheers,
              tod

It appears that the UI default value setting capability available
through the table editor/designer is not propagated to the underlying
database by design, see this bug report :

http://openoffice.org/bugzilla/show_bug.cgi?id=108100

And it also appears that this will not be fixed any time soon, at least
not in the OOo code, given the work that would be required to fix it, so
it is probably even less likely to be done in the LibO code where there
are no specialist db developers AFAIK.

Currently, the only correct way to set a default value in the underlying
db is to issue a corresponding CREATE TABLE or ALTER TABLE statement via
the Tools - SQL menu entry.

Alex

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#10

Hi Tod,

I would very much like to use Base, but I'm at the edge of having sufficient knowledge to make it work. It appears that in order to make Base work for me, I will have to study MySQL and use it as my backend, with base as a front end.

Well, it isn't an absolute requirement to use a db server to get
something useful out of Base, but if you want to carry on using HSQLDB
(as provided by LibO or in its latest version incarnation of 2.0), then
I would strongly advise you to read the tutorials on the OpenOffice.org
forum about setting up mixed-mode functionality. At present, even using
mysql has its quirks/problems when working from within LibO/OOo, but so
far, with my own use of mysql, the only things I've managed to kill in
the past have been my ODB files (most notably forms) and not my data.

Alex

#11

Thanks for the advice. By "mixed-mode" you mean the use of HSQLDB front end with MySQL (or other) backend?

I've been trying to read what documentation there is. Not much. I find that as soon as I get beyond what I already understand, there is a presumption that I that I have a working knowledge of SQL, which I don't.

So, since my goal is multi-user database, for which I now see that I need MySQL anyway, I figure I should turn to learning MySQL.

Cheers,
             tod

Hi Tod,

I would very much like to use Base, but I'm at the edge of having sufficient knowledge to make it work. It appears that in order to make Base work for me, I will have to study MySQL and use it as my backend, with base as a front end.

Well, it isn't an absolute requirement to use a db server to get
something useful out of Base, but if you want to carry on using HSQLDB
(as provided by LibO or in its latest version incarnation of 2.0), then
I would strongly advise you to read the tutorials on the OpenOffice.org
forum about setting up mixed-mode functionality. At present, even using
mysql has its quirks/problems when working from within LibO/OOo, but so
far, with my own use of mysql, the only things I've managed to kill in
the past have been my ODB files (most notably forms) and not my data.

Alex

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#12

Hi :slight_smile:

Our Documentation Team will need volunteers that have some understanding of
Base.

There is likely to be help available in transferring OpenOffice's community
documentation into our Alfresco content management system. Documentation goes
through a series of stages before reaching proof-reading. A document is
downloaded from Alfresco, edited in Writer or something and then re-uploaded
either to the same stage or moving it on one stage until it reaches final
proof-reading. Screen-shots can't be done in Windows but that still leaves a
lot of small edits that can make a huge difference.

If anyone following or involved in this thread is willing to give it a try then
please feel free to join the documentation teams mailing list.

Regards from
Tom :slight_smile:

#13

Hi Tod,

Thanks for the advice. By "mixed-mode" you mean the use of HSQLDB front end with MySQL (or other) backend?

Sorry, I should have made myself clearer. By mixed-mode of HSQLDB, I
meant that the hsqldb.jar (which is provided with LibO and OOo as the
built-in database engine) can be used in client (aka file) and server
mode depending on the parameters given to it on start-up, providing
certain tweaks are carried out beforehand. In file mode, only one user
can access the db at any given time. However, in server mode, you can
have concurrent multiple user access.

An explanation of how to set this up is provided in a tutorial available
on the openoffice.org forum :

http://www.oooforum.org/forum/viewtopic.phtml?p=396523#396523

If you really want to stick with hsqldb as the database engine, then you
should go and read through this material.

I've been trying to read what documentation there is. Not much. I find that as soon as I get beyond what I already understand, there is a presumption that I that I have a working knowledge of SQL, which I don't.

So, since my goal is multi-user database, for which I now see that I need MySQL anyway, I figure I should turn to learning MySQL.

Well, mysql as a backend is but one alternative, and as I mention above,
not the only one that you can use if you want multiple user, concurrent
access to the db. Your base file (ODB file) then becomes a front-end
"container" for the backend server. I suppose the main advantage of
using mysql as a back end with LibO is that the native mysql connector
provided as an installable extension enables fairly comprehensive
management of the different data types supported by mysql and actually
pretty good performance without having to tweak cache memory settings
and whatnot. It still has its "gotchas" though, in fact all of the
available connectors (ODBC/JDBC) for mysql do. Unfortunately, these are
not widely documented, and often can only be found by trawling through
bug reports on multiple sites.

Alex

#14

MySQL is quite simple once you get started. Makes it much easier with a tool like Webmin.
We started extensively with the old Lotus Approach and then migrated to PHP/MySQL for general cross platform browser access. I keep looking at Base, but it hasn't reached the state of Approach so haven't dived in.
steve

#15

That's a huge help, thanks. I suppose this raises the question, why does Base default to file mode? Simplicity?

merci,
              tod

Hi Tod,

Thanks for the advice. By "mixed-mode" you mean the use of HSQLDB front end with MySQL (or other) backend?

Sorry, I should have made myself clearer. By mixed-mode of HSQLDB, I
meant that the hsqldb.jar (which is provided with LibO and OOo as the
built-in database engine) can be used in client (aka file) and server
mode depending on the parameters given to it on start-up, providing
certain tweaks are carried out beforehand. In file mode, only one user
can access the db at any given time. However, in server mode, you can
have concurrent multiple user access.

An explanation of how to set this up is provided in a tutorial available
on the openoffice.org forum :

http://www.oooforum.org/forum/viewtopic.phtml?p=396523#396523

If you really want to stick with hsqldb as the database engine, then you
should go and read through this material.

I've been trying to read what documentation there is. Not much. I find that as soon as I get beyond what I already understand, there is a presumption that I that I have a working knowledge of SQL, which I don't.

So, since my goal is multi-user database, for which I now see that I need MySQL anyway, I figure I should turn to learning MySQL.

Well, mysql as a backend is but one alternative, and as I mention above,
not the only one that you can use if you want multiple user, concurrent
access to the db. Your base file (ODB file) then becomes a front-end
"container" for the backend server. I suppose the main advantage of
using mysql as a back end with LibO is that the native mysql connector
provided as an installable extension enables fairly comprehensive
management of the different data types supported by mysql and actually
pretty good performance without having to tweak cache memory settings
and whatnot. It still has its "gotchas" though, in fact all of the
available connectors (ODBC/JDBC) for mysql do. Unfortunately, these are
not widely documented, and often can only be found by trawling through
bug reports on multiple sites.

Alex

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Tod Hopkins
Hillmann & Carr Inc.
todhopkins@hillmanncarr.com

#16

Why can't Windows screen shots be accepted for the documentation? Is the
Windows
version of LibO that much different from the Linux and Mac versions?

John

#17

John

> Hi :slight_smile:
>
> Our Documentation Team will need volunteers that have some understanding of
> Base.
>
>
> There is likely to be help available in transferring OpenOffice's community
> documentation into our Alfresco content management system. Documentation
> goes
> through a series of stages before reaching proof-reading. A document is
> downloaded from Alfresco, edited in Writer or something and then
> re-uploaded
> either to the same stage or moving it on one stage until it reaches final
> proof-reading. Screen-shots can't be done in Windows but that still leaves
> a
> lot of small edits that can make a huge difference.
>
>
> If anyone following or involved in this thread is willing to give it a try
> then
> please feel free to join the documentation teams mailing list.
>
>
> Regards from
> Tom :slight_smile:
>
Why can't Windows screen shots be accepted for the documentation? Is the
Windows
version of LibO that much different from the Linux and Mac versions?

John

I am not sure what he meant, a screenshot will show the information
common to both. If a Linux of Mac screen shot is used you might need to
edit it to avoid confusing a Windows user who is not familiar with those
desktops

#18

Hi John,

Why can't Windows screen shots be accepted for the documentation? Is the
Windows
version of LibO that much different from the Linux and Mac versions?

It has nothing to do with differences in versions, but rather Microsoft
Corp's unwillingness to allow use of parts of its UI in screenshots for
free (as in "libre") documentation. This has been previously discussed
on the LibO Documentation mailing list, and other LibO lists, as well as
several years ago on the OOo community mailing lists.

Alex

#19

Hi Steve,

MySQL is quite simple once you get started. Makes it much easier with a
tool like Webmin.
We started extensively with the old Lotus Approach and then migrated to
PHP/MySQL for general cross platform browser access. I keep looking at
Base, but it hasn't reached the state of Approach so haven't dived in.
steve

Yes, Base is still one hell of a long way from anything near what
Approach was or FileMaker Pro, for that matter. It is a shame that IBM
did not pursue the Approach way of doing things when it decided to put
its money into developing Lotus Symphony.

Alex

#20

Hi John,

[...]

>
Why can't Windows screen shots be accepted for the documentation? Is the
Windows
version of LibO that much different from the Linux and Mac versions?

It's not because it is so different from Mac or Linux versions but because Microsoft has a very certain view about copyright and using screenshots made on a Windows system in the documentation for a competing product.

The germanophone OOo project asked MS Germany about this and the answer we got was that we would need permission from MS. (André, if I'm wrong, please correct me). So to avoid any copyright issues we decided to use only screenshots made under Linux.

Sigrid