Table View - Column Names

[NYPoke]

I am trying to convert a List View Layout into a Table View. Love the functionality of the Table View. Users love.

However, I can't get the Column Names set. They are using the Database Field Names, which aren't very user friendly.

In the Inspector, I found an entry, under Positions, for Name. However, the Table doesn't use this for the Column Name.

Great functionality, but I don't want to rename the Database Fields.

Any suggestions?

[Ocean West]

Unfortunately no - you will need to create a LIST view if you wish to have your own names

for the column / field names.

[Rramjet]

A bit more work, but... What about creating a new layout (a Header and a Body) with the required fields in a row in the Body (as in Table View) and the column names (as text boxes) in the Header directly above the fields. You can then assign sort by functions to each of the column names. The advantage of this is that you can also place navigation buttons, function buttons, Record number displays, etc in the header, giving you all the functionality of a Table View with added bonuses.

I have done this and it works really well (users love it even more than the standard Table View). I also include a Checkbox field (value list "1") and Mark, Find and Clear Checkbox (scripted) buttons in the header above the Checkbox field.

[NYPoke]

Yes, we have the Header & Footer on the layout. Much nicer than the Version 6 Tables (don't think you could use Header/Footer in 6, but I could be wrong).

We had the Column Headers in the Table, for List View. So far however, the Table View forces the Column Names in there, unless I just haven't found the magic.

I just wanted to change the names for that first row. If I could get rid of the row, that would help also.

[Rramjet]

I am not sure I understand your intentions here. I was talking about a NEW STANDARD layout containing just a Header and a Body (Layouts > New layout/Report > Standard Form... and follow the prompts...) and at the end delete the Footer and arrange the fields in a row in the Body - closing the Body up to show/contain just/only that row of fields - and place the field names into the Header just above the respective row of fields - editing them to plain English. Then assign Sort by functionality to the Header names. Resize the Header so you can add a title, navigation, function, etc as you wish. Then to your original layout add a button that takes you to the NEW Layout and in the NEW layout add a button that takes you back to your original Layout.You then don't have to mess around with the various "views" in FMP... (I have also found it useful to actually script the navigation buttons between the two layouts to pick up and display the current record client going in and Show All going out. I also include a script on a client name in the NEW "LIST" layout so that clicking on the name takes you to the individual record in the original layout.

[NYPoke]

Well, I could do that, but the Version 11 Table View builds in the headers for me. They track with any changes, unlike building your own headers.

I don't have the time to build headers for all the layouts, while switching them to Table View makes is easy & it all tracks together as we make changes.

Just...can't...control...the...column names, easily.

I did find the place to turn off the header row, but that leaves me back with building my own headers.

I'll get some sleep & re-read your posts again tomorrow. I might not be absorbing it all.

Thank you though.

[Ocean West]

I'd recommend not using table view unless you have adequate security implemented or highly trusted users - as switching a layout to table view allows end users to modify the schema of the underlying table. (adding / deleting fields ) also they can accidentally add records bypassing any scripted button you may have required.

Also if you have merged fields on a layout they become 'editable' on the table view.

Mostly however for the reason you are experiencing that the "database field names" are reflected in the column label and they most likely are not necessarily human readable.

Stephen

[NYPoke]

After sleeping on it & thinking about it, table view isn't going to be the way to go. Kind of cool, but as Stephen says, it has inherent security problems.

After realizing that the users can simply right click on any field & sort, we don't get too much out of table view.

Will leave the list views in place & point them towards the easy right click for sorting.