Issue 53282 - "form as table" view seems to have arbitrary and illogical column order
Summary: "form as table" view seems to have arbitrary and illogical column order
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m122
Hardware: PC Windows 2000
: P3 Trivial with 3 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-08-13 23:26 UTC by helgekraak
Modified: 2017-05-20 10:44 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description helgekraak 2005-08-13 23:26:34 UTC
As the summary already says it, you can't change the order of the database table
columns in the datasource view connected to a form. I open this table on the top
of the form e. g. with

document   = ThisComponent.CurrentController.Frame
dispatcher = createUnoService("")
dispatcher.executeDispatch(document, ".uno:ViewFormAsGrid", "", 0, Array())

I would very very much appreciate if you could bring this feature into the next
version! I'm sure that a lot of other people will also stumble over this missing
feature, above all when the final release is out and people will experiment with
the new form / database features.

Best regards
Helge Kraak
Comment 1 helgekraak 2005-08-13 23:33:13 UTC
I forgot to say, that it would already be a big improvement, if the columns
would follow the tab activation order you set in the form fields. Until now I
don't see any logic behind the column order (e.g. alphabetical arrangement or
something similar). it seems to me that the order at the moment is taken from
the order in which you created the form fields. I only estimate, didn't verify
it myself.
Comment 2 Frank Schönheit 2005-08-15 08:12:10 UTC
changing summary from
  Datasource view of form connected table not influencable regarding the column
  "form as table" view seems to have unchangeable,  arbitrary and illogical
column order

(Helge, if this doesn't completely meet the problem you mean, we have to change
again :)

Yes, in fact the order is taken from the "logical" order of controls within
their form (see the form navigator), which usually is the order in which the
fields were created.

And no, there won't be any fix for this in OOo 2.0, sorry, but in the current
phase (near the release), it's simply not important enough anymore.
Comment 3 helgekraak 2005-08-15 08:30:24 UTC
Hi Frank,

your new description meets the problem very good. Thank you :-)!
Comment 4 Marcus 2017-05-20 10:44:42 UTC
Reset the assignee to the default "".