Le ven 06/08/2004 à 11:36, jeannelle-d a écrit :

Bonjour,

Trouvé sur http://www.oooforum.org/forum/viewtopic.php?t=5059

________________________________________________________________________ Without understanding why, I have isolated what causes OOo to cause the SQLBindParameter error. It is caused by having a UNIQUE KEY in a table in an INNODB database. The error doesn't happen all the time, but most of the time. Sometimes also in Writer, too. Removing the line: "UNIQUE KEY title (title)," from the table definition 'fixes' it. Unfortunately I need two columns to be unique so this isn't helpful. I have worked round this by removing the PRIMARY KEY from an auto_increment column, and just un-enabling that field on my forms, and putting the PRIMARY KEY on the previously UNIQUE KEY column. This doesn't stop the supposedly unique number column from getting updated directly, however.

Has anyone else experienced problems with UNIQUE KEYS and OOo and is there any proper fix for it?

Et la suite :

I've experienced the same problem myself. I just discovered the source as the UNIQUE key index today.

I've had the same trouble while trying to use forms, but oddly enough only after I do a refresh of the datasource connection. Prior to that I can edit away to my heart's content. One refresh and I get the "SQLBindParameter not used for all parameters" error.

Voilà ce que j'ai trouvé pour l'instant.

Alex