Issue 23992 - Deleting fields in ODBC Access data source cause Ooo crash
Summary: Deleting fields in ODBC Access data source cause Ooo crash
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: PC All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: christoph.lukasiak
QA Contact: issues@dba
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-30 18:39 UTC by hwoarang
Modified: 2006-05-31 14:29 UTC (History)
3 users (show)

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


Attachments
My database that make Ooo crash (16.24 KB, application/octet-stream)
2004-02-25 17:31 UTC, hwoarang
no flags Details
the same database without password (16.24 KB, application/octet-stream)
2004-03-02 16:03 UTC, hwoarang
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description hwoarang 2003-12-30 18:39:05 UTC
Hi, sorry if I posted in wrong place... 
How to reproduce:
Open Data Sources (View -> Data Sources)
Create a DataSource (in my case with a MsAccess database)
Select a table
Click in the top left button (to select all the table)
Hit Del

Ooo will crash

Another way:
Open any table
Select all fields (including the last in blank)
Hit Del

Ooo will crash

Using Ooo 1.1.1a in Windows 98
Comment 1 marc.neumann 2004-01-05 08:19:46 UTC
Hi,

-> clu: can you please have a look on this with a MSAccess datasource. With a
dbase and mysql datasource the crash doesn't happend.

bye marc
Comment 2 christoph.lukasiak 2004-01-05 12:37:22 UTC
clu->hwoarang: sorry, cannot reproduce - the reason must be something you have
not described - do you connect over ADO or ODBC? - does it crash with every
table or only with special, does it also crash with other data sources?
Comment 3 hwoarang 2004-01-05 14:38:14 UTC
I'll try with another datasource, but it happens with any table...
I connected by ODBC and all operations go just fine: select, update and delete 
(by sql), filters, sorts with DataSources dialog...
But when I do the steps that I described, the crash come...
I'll test with other datasource and see what will happens...
Thanx
Comment 4 hans_werner67 2004-02-02 12:15:18 UTC
change subcomponent to 'none'
Comment 5 christoph.lukasiak 2004-02-25 09:57:23 UTC
CLU->All: can anybody else acknowledge this behavior and write a reproduceble
step by step description for this problem - for me it works still fine
Comment 6 hwoarang 2004-02-25 15:17:34 UTC
hwoarang -> CLU:
do you want that I send the crash report to you?
I can create a database with one table and attach here too...
what is much easy?
Comment 7 christoph.lukasiak 2004-02-25 16:01:32 UTC
CLU -> hwoarang: both would be great
Comment 8 hwoarang 2004-02-25 17:28:43 UTC
hwoarang -> CLU: Ok.. I'm sending the crash resport to your e-mail, because is 
to big to post here, ok?

And I attaching my .mdb file with just one table (I deleted the others for size 
matters).

Thanx
Comment 9 hwoarang 2004-02-25 17:31:15 UTC
Created attachment 13432 [details]
My database that make Ooo crash
Comment 10 christoph.lukasiak 2004-03-01 15:21:32 UTC
CLU->hwoarang: like i have written in private e-mail: please always use the
crash report generator to send the reports - please stay here on oo with your
postings (else this task will not be understandable for all other) thx
Comment 11 christoph.lukasiak 2004-03-02 11:26:00 UTC
CLU->hwoarang: sorry, i cannot find your crash report in our crash library -
please send it again with your e-mail adress (please always use your oo adress)
- after that you get an e-mail with an report id - it would be nice, if you
could add this id to this task
Comment 12 christoph.lukasiak 2004-03-02 15:20:09 UTC
CLU->hwoarang: the attached data source seems to be password protected - please
send a 'clean' data source or public the used password

thx
Comment 13 hwoarang 2004-03-02 16:03:04 UTC
clu: sorry for the password... I attaching the db without pwd...

I sent another crash report right now, I already receive the reply from Oo but 
I can't find any 'report ID' to tell you...

what now ?

Hwoarang
Comment 14 hwoarang 2004-03-02 16:03:43 UTC
Created attachment 13535 [details]
the same database without password
Comment 15 christoph.lukasiak 2004-03-02 16:51:23 UTC
CLU->hwoarang: sorry, my fault - you don't get an id (i find you over your
e-mail adress) - your job is hopefully done for this task - thank you for your
patience
Comment 16 christoph.lukasiak 2004-03-02 16:58:18 UTC
CLU->OJ: your turn

short repro:
1. create a data source with attatched data source over ODBC
2. open database beamer with proper source
3. mark whole table (upper left corner) and delete content (with del key)
-> crash
Comment 17 christoph.lukasiak 2004-03-02 16:59:16 UTC
set target
Comment 18 christoph.lukasiak 2004-03-02 17:01:08 UTC
repro on winxp
Comment 19 hwoarang 2004-03-02 18:39:15 UTC
I glad that I could help with this issue...
Now I'm working to help with #25875, because I'll must send another database 
with some data in Calc document to your tests...

Thanx
Comment 20 hwoarang 2004-03-04 19:54:15 UTC
Making some tests here, I notice the error just happens in some tables, others 
not...
After some checks I think I found the reason: 
The crash only occurs if the table has a Memo field...

Hope this helps...

Hwoarang
Comment 21 hwoarang 2004-03-23 12:45:07 UTC
hmmm...
if the table has Yes/No [BIT] fields, the crash come too...

testing now with OOo1.1.1rc3
thanx

Hwoarang
Comment 22 ocke.janssen 2004-05-13 08:22:07 UTC
Not repro, in cws insight01.

Seems to be fixed by another bug. 
OJ->CLU: Please verify this. Thx.

Best regards,

Ocke
Comment 23 marc.neumann 2004-06-15 10:56:36 UTC
reopen
Comment 24 marc.neumann 2004-06-15 10:57:05 UTC
reassign to clu
Comment 25 marc.neumann 2004-06-15 10:57:28 UTC
fixed in CWS insight01 -> please verify
Comment 26 christoph.lukasiak 2004-06-16 15:21:18 UTC
cannot be tested before issue 30345 is not fixed
Comment 27 christoph.lukasiak 2004-07-06 10:46:56 UTC
CLU: next issue 31135 block verification of this one
Comment 28 christoph.lukasiak 2004-07-06 12:48:06 UTC
CLU->OJ: still occurs in cws (if you follow my instruction)

crash report: rzk7u9 (in current cws: insight)
Comment 29 christoph.lukasiak 2004-07-06 12:50:16 UTC
CLU->OJ: your turn again
Comment 30 ocke.janssen 2004-10-07 09:17:17 UTC
Fixed in cws dba16
Comment 31 ocke.janssen 2004-10-13 08:46:47 UTC
Reopen for QA
Comment 32 ocke.janssen 2004-10-13 08:47:02 UTC
Please verify. Thanks.
Comment 33 ocke.janssen 2004-10-13 08:47:14 UTC
Set to fix again
Comment 34 christoph.lukasiak 2004-10-20 10:20:55 UTC
verified in cws
Comment 35 christoph.lukasiak 2004-11-29 14:24:54 UTC
verified in master (680m63)
Comment 36 hwoarang 2004-12-07 11:04:33 UTC
Hi !
If I'm not wrong, this fix will be available only in 2.0 ?
Because in 1.1.4rc is happening again.
I sent a crashreport in this moment.

Thank you.
Hwoarang
Comment 37 hwoarang 2004-12-07 11:12:40 UTC
Hi !
If I'm not wrong, this fix will be available only in 2.0 ?
Because in 1.1.4rc is happening again.
I sent a crashreport in this moment.

Thank you.
Hwoarang
Comment 38 Frank Schönheit 2004-12-07 14:10:15 UTC
> If I'm not wrong, this fix will be available only in 2.0 ?
Exactly.
Comment 39 hwoarang 2005-09-08 14:40:53 UTC
this issue is back on m128.

with m125 was working fine.
now (with m128) OOo crash and there's no crash report to send

Hwoarang
Comment 40 Frank Schönheit 2005-09-26 12:32:14 UTC
this was issue 54394 and will be fixed before 2.0 release