Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Relationships not stored | ||||||
---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | brenno <brenno> | ||||
Component: | code | Assignee: | dbaneedsconfirm <needsconfirm> | ||||
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@dba <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | alex.thurgood, frank.schoenheit, issues, philipp.lohmann, stephan_schaefer | ||||
Version: | OOo 3.0 Beta | Keywords: | aqua | ||||
Target Milestone: | --- | ||||||
Hardware: | Mac | ||||||
OS: | Mac OS X, all | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
brenno
2008-05-07 15:13:28 UTC
I am using 3.0 Beta on MAC OS X (Aqua) and am having the same problem. After creating a simple relational database file, I set a relationship that is 1:n. Sometimes, the 1:n will show in the line showing the relationship, and sometimes it will not. Sometimes when opening the relationship, even the line showing the relationship has disappeared. Then I created a form with a subform. Even though I entered info into both the form and subform, the no data corresponding to its particular record appears. The data appears correctly in the tables. I had the same problem with this same file when opening it with 3.0 Beta (Linux [Debs]), but OOo 2.4 opened it correctly as has the m19 developer version. The file: bp.odb will be uploaded shortly to demonsrate the problem. Created attachment 54496 [details]
Testcase for showing relationships using 3.0 Aqua on OS X
clu->wurzel: may you have a look at this one thx wurzel > clu : I have just tried to reproduce this in beta 3.0 m3 and confirm the behaviour. When you first open the file supplied, the relation is present and shows up when you go through the Tools > Relations menu. If you delete the relation, by selecting it and then pressing Ctrl-mouse button, you can not re-establish it by dragging and dropping, nor via the menu. When you quit the relations designer, it asks if you want to save : if you reply "no", then re-open the relations designer window, the relation is gone. Haven't tested this in Linux, but can definitely confirm on Mac. To whom does this get re-assigned, clu ? Apologies if I am doing this wrong - I am completely new to this forum. I have a similar problem Mac OSX 10.4.11 OpenOffice 3.0.0 Beta. I have two tables When I go Tools > Relationships I cannot create a relationship by click and drag. The relationship line does not form at all. I have opened the database in OpenOffice 3.0.0 Beta under Windows and the relationship forms as expected. I suspect this is the same issue, but if not let me know so I can file a new one. Hi aggeniator, Yes, this is exactly what I tried as well, so you have essentially re-confirmed what I confirmed in the first place, so no need to open another issue. My guess is that this is a Mac porting issue, there is another one I opened recently about dragging and dropping field names to Writer documents not working. The same visual symptons appear, i.e. the cursor becomes a dot on the screen that can be dragged about, but which doesn't actually do anything. However, I suspect that the visual display error is a result of the absence of the underlying functionality. Thanks for your help !! Alex Changed version to Beta 3.0 because this is the next slated public release and it will need fixing on Mac before that can happen (IMHO). Alex A related drag'n drop issue (or may be a duplicate) is #90747. The first and the second comment in the bug description say that relations you add (or which are already existent) are not stored, i.e. when you re-open the relation designer, then they're gone. This in fact would *not* be the same as issue 90747. However, all subsequent comments seem to indicate that people have the problem that they cannot add relationships via drag and drop, which in fact *is* a duplicate of issue 90747. I could reproduce the second problem (which pl meanwhile fixed), I could not reproduce the first problem in m26. So, unless somebody objects, I suggest closing the issue as WORKSFORME, since in a recent build, the original problem cannot be reproduced, and the secondary problem brought up here is covered elsewhere. -> worksforme -> close |