Issue 120431 - ODBC generates a "cursor error" when the modification switches the record out of the "visible" recordset (filter rules)
Summary: ODBC generates a "cursor error" when the modification switches the record out...
Status: UNCONFIRMED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 3.4.0
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-01 14:40 UTC by tansu
Modified: 2013-01-29 21:47 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description tansu 2012-08-01 14:40:27 UTC 
While editing a table, after a few filters have been applied, if a modification leads the record to get out of the "visible" recordset, there is an error message and the record is still visible even though it can't be modified. The filters have to be reset and applied again to fix the situation.

Example: I show only records with Status="OK". On one record and change status to "Not OK". This will show the following message : 
- Erreur lors de l'écriture de l'enregistrement actif
- Statut SQL: 24000 [Microsoft][Gestionnaire de pilotes ODBC] État de curseur non valide
Comment 1 r4zoli 2012-08-15 08:52:11 UTC 
Change component, not connected to bug.
Some bug happened with the "non visisble" records in AOO 3.4 which is possibly solved in 3.4.1 development. Please check it if AOO 3.4.1 came out or test AOO 3.4.1 development build: https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds