Read this if you cannot insert/delete/update records

[avantman42]

This problem seems to come up quite often, so I'm posting this sticky thread to try and enable people to find the answer more easily.

If you have a database, and you are having problems like not being able to add new records or delete/update existing records, then your database might be being opened read-only. This might be because some database drivers return incorrect, or insufficient, information regarding privileges. This problem is commonly reported with MySQL, but can affect other databases too.

More information can be found on OOo's Database Access project web site at:
http://dba.openoffice.org/FAQ/FAQ.html#dataupdate
http://dba.openoffice.org/howto/IgnoreDriverPrivileges.html

The above links describe how to use a macro to work around the problem. I've written a document that makes it easy to apply the neccessary changes. You can get it from OOoMacros:
http://www.ooomacros.org/user.php#103772

Russ

[Luctor]

I've tried your macro and I've searched in my files and found a file called

[Luctor]

I've tried to do a SQL query from OOo and that works ...

[avantman42]

Sorry, I don't know what is going wrong I'd suggest you try asking in the Data Sources forum.

Russ

[moptop99]

russ, thank you for this excellent macro, I was pulling out my heair, this is great. Unfortunately the OOo installed on one of my machines seems to crash every time I run a macro -- don't know yet what the problem is there. But in the meantime was wondering whether there's an xml file somewhere that I can edit manually to change the privileges. presumably the info exists somewhere?

thanks,

Matt

[avantman42]

[kbrown]

Tried everything suggested above but no avail. Switching from MyODBC to MySQL Connector/J solved the problem though...

[Celsun]

For over the past year-and-a-half, OOo, MySQL, and ODBC worked correctly for me. Recently, after upgrading to a new Linux OS, different computer, and newer versions of MySQL, ODBC, and MyODBC, tables were “read-only.”

Needless to say, this was very frustrating. Trying the things suggested in this forum didn't correct the issue.

To shorten this little story, what worked for me, and maybe will for others as well is:

Changing the owner from “root” to “mysql” on the databases that were backed up and restored to /var/lib/mysql.

Celsun

[cyberwuffy]

The macro didn't work with my tables after I set ignore privledges. They're still in read only. I love the new beta simply because of its database program, but this is an awful lot of hassle. Can't the M$ Access database simply be converted to an Open DataBase file?
_________________
Best Wishes,
Cyberwuffy Ala Wolfe

Sysinfo:
Debian Linux; OO 2.3

[mercurus]

Hi

I've been having problems with MySQL and OO,o 1.1.3 (Debian, 2.6.11) - until now.

I got ODBC and MySQL communicating quite satisfactorily but I wasn't able to edit the data in OO.o, nor could I access field names for use in a mail merge.

Solution ?

I read this post: http://www.oooforum.org/forum/viewtopic.phtml?t=10509&highlight=mysql+mail+merge

To summarise, it is critical that your table and field names DO NOT CONTAIN SPACES. As soon as I changed all my tables and fields to use underscores "_" rather than spaces " " all worked perfectly.

[Lunar]

using OO 1.9.95 trying to migrate a simple Access 2000 home database to Base, importing just the one table and creating a form. Using ODBC database views fine but always opens in read-only. Found problems adding records and sometimes with other functions. Changed to "edit mode" so read-only didn't appear made no difference. All problems were resolved when I checked that any added/edited record did have a valid record ID, not <autofield> (enforce this simply by moving back one record then forward again) --if it did then all changes saved without problems --read-only mode was irrelevant as, just as in Access, changes are automatically saved. This problem does not occur if entering data in a table but then who ever does that...

PS Echo previous poster about spaces in table/field names. You'll notice that if you use the wizzards you won't and that's why!

[lynx]

Just started using OOo for a database. Managed to keep adding data (eventually), but any directory (folder--XP) I saved in now is apparently irreparably read-only. Sneakily changes BACK to read-only after claiming to have rewritten attributes. Deinstalled and deleted everything, can't find anything weird. Don't see any changes in user permissions. ??? first dBase, then saved data as spreadsheet, same problem...still a driver issue?
Help?
lynx

[frazelle09]

Tried the downloaded macro to see if it would help in getting a newly formed db to accept data input through a query or form. Two of the tables are related (one to many - inner join), both have a primary key which is indexed and none of them have table or column name with spaces. I even went back to EMS PostgreSQL Lite to set permissions on all tables and did a reset of the computer, but am still unable to input the first record into the two tables through the query or form-subform. Any other ideas? Am using Postgresql and the Postgresql SDBC driver. Have a happy week!!
_________________
Now using 3.2.1 on 4 PCLinuxOS 2010 boxes (two are laptops).

"The earth is one country and mankind its citizens."
Bahá'u'lláh

"La tierra es un sólo país y la humanidad sus ciudadanos."
Bahá'u'lláh

[bailey]

I am hesitant to use the macro or download any drivers. I am not familiiar with macros, and I don't have very much experience with databases. Since I just started working with OOo Base, is it possible that I am not opening the database correctly? Thank you, Bailey

[EtHeReAl]

I've the same problem!

I've a table that, opened, is read-only...

I cannot modify or add new values or entries...

I've tried with the macro you linked, but it didn't work...

Do I have to abandone every hope?