Issue 14719 - OOo Base said (ungueltiger Cursorstatus)
Summary: OOo Base said (ungueltiger Cursorstatus)
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC4
Hardware: PC Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2003-05-21 21:05 UTC by holgerbruenjes
Modified: 2006-05-31 14:29 UTC (History)
2 users (show)

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

Attachments
The Original (23.34 KB, text/plain)
2003-06-14 16:26 UTC, holgerbruenjes 		no flags Details
The mistake (25.53 KB, text/plain)
2003-06-14 16:27 UTC, holgerbruenjes 		no flags Details
After 9 promptet and reload (32.21 KB, text/plain)
2003-06-14 16:28 UTC, holgerbruenjes 		no flags Details
the MySQL dump (2.28 KB, text/plain)
2003-06-14 16:28 UTC, holgerbruenjes 		no flags Details
the form/subform (8.54 KB, text/plain)
2003-06-14 16:29 UTC, holgerbruenjes 		no flags Details
the datasource manager (25.34 KB, text/plain)
2003-06-14 16:30 UTC, holgerbruenjes 		no flags Details
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 holgerbruenjes 2003-05-21 21:05:35 UTC 
I work with MySQL, ODBC and OOo, so I have a form und a subform with
autoincrement. I work with the MySQL Data Source Sheet.
When I will insert a new record OpenOffice.org Base said (Error inserting the
new record) Microsoft(ODBC DataManager) ungueltiger Cusorstatus.
And now the field was not free and I can not work, but the record was written in
the Database. When I look auf my Database out of OOo the record was 9x in the
Database, when I have promtet 9x.
Comment 1 Frank Schönheit 2003-05-22 07:33:44 UTC 
correcting component (see
http://www.openoffice.org/issues/describecomponents.cgi?component=database%20access)
asigning to QA
Comment 2 Frank Schönheit 2003-05-30 10:43:48 UTC 
Holger, could you attach a dump of the MySQL tables in question (use
mysqldump for this), and the form which produces the error? Your
current bug description contains some uncertainties, and I think it
would be easiest if you could provide us the concrete document/data
which causes the bug.
Comment 3 holgerbruenjes 2003-06-14 16:26:26 UTC 
Created attachment 6877 [details]
The Original
Comment 4 holgerbruenjes 2003-06-14 16:27:16 UTC 
Created attachment 6878 [details]
The mistake
Comment 5 holgerbruenjes 2003-06-14 16:28:14 UTC 
Created attachment 6879 [details]
After 9 promptet and reload
Comment 6 holgerbruenjes 2003-06-14 16:28:53 UTC 
Created attachment 6880 [details]
the MySQL dump
Comment 7 holgerbruenjes 2003-06-14 16:29:32 UTC 
Created attachment 6881 [details]
the form/subform
Comment 8 holgerbruenjes 2003-06-14 16:30:15 UTC 
Created attachment 6882 [details]
the datasource manager
Comment 9 holgerbruenjes 2003-06-14 16:35:17 UTC 
MySQL 3.23.47
MyODBC 2.50.39
Comment 10 holgerbruenjes 2003-06-15 14:19:03 UTC 
The same problem unter SuSE 8.1 
MyODBC 2.50.39-1.i386.rpm
Comment 11 holgerbruenjes 2003-08-17 14:19:36 UTC 
in 1.1.0rc3de tritt der Fehler nicht mehr auf
Comment 12 holgerbruenjes 2003-08-17 19:46:58 UTC 
Change to Linux (Win98SE ist mit 1.1rc3 OK)
Comment 13 holgerbruenjes 2003-09-14 14:24:08 UTC 
change to 1.1.rc4
Comment 14 andreschnabel 2003-11-15 14:43:39 UTC 
adding myself to cc, trying to verify
Comment 15 andreschnabel 2003-11-16 11:43:37 UTC 
this issue is likely to be a duplicate of Issue 17123 .

I'll contact Holger directly and come back if i have more infos.
Comment 16 marc.neumann 2003-11-17 08:50:18 UTC 
add keyword needmoreinfo
Comment 17 andreschnabel 2003-11-20 18:57:14 UTC 
I resolve this issue with "worksforme", as holger was able to get this
working when using MyODBC 3.51.06 .

As there are some related issues I didn't check yet I will not close
the issue.

Here is a list of realted issues, collected by Dian Mackay at dev@qa:
Issue 5450, Issue 17123, Issue 22374, Issue 21828, Issue 17218
Comment 18 christoph.lukasiak 2003-11-24 10:51:53 UTC 
CLU->Andre Schnabel: i do not see a reason, not to close this issue ->
looks definetly like a driver problem (can be fixed with new driver!)
even if this issue would have anything to do with the other issues
(does not look like), it would probably be double to them and closed, too.

summary: 17218 and 21828 are double to 17123 (one bug) - 22374 looks
like a driver problem, too (no bug) -> so 17123 and 5450 are the
'real' bugs (look similar, but OJ as developer has to decide over
this) and will be fixed as fast as possible

also it is every time possible to reopen this task, so i close this issue

thank you for your engagement
Comment 19 hans_werner67 2004-02-02 12:26:05 UTC 
change subcomponent to 'none'