Richarddunbarx wrote: ↑Wed Nov 13, 2019 5:16 pmRichard suggests table fields. I like table fields.
But you have to massage a new table field before it is stable. See this:
viewtopic.php?f=7&t=31452&p=170731&hili ... ly#p170731
Once properly set up, these fields are very easy to use.
Craig
I'm going to address all related comments here regarding the table field. I did view the linked posts and the video and I saw Craig's fix for the problem described (and I could implement it, but it might be unsustainable for someone at my level of skill with LC, since I don't really know what's happening with it).
I would love to use a table field (or anything) rather than a datagrid for sure. It looks more like a simple spreadsheet and is way easier to handle as an object (no copy problems, attached templates, etc). But selecting and editing a table field via the keyboard seems just as problematic as the data grid. Once you click on it you're fine, but adding rows and getting to the next row and doing column totals and such seem like quite a task. I don't see the documentation on this.
A gentleman troubled himself to do a prettified table field template which I borrowed, but you still can't do headers, which kind of negates its use as a spreadsheet. I suppose you could put them at the top of a loop like you do in php when reading a database table, but that seems tailored to bite you in the posterior down the road when you're trying to do column totals and refreshes.
Bottom line, I'd be glad to return to this option if someone could point me to documentation I haven't seen yet. The main deficit I see so far is that a "column" in a table field is really just a tab and in the data grid at least it seems to be an object, and a field (thanks to Michael Bluejay) can be addressed as row instance of a column.
FYI: I'm on Mac Sierra using Community Plus 9.01 and Commercial 5.5, and I've noticed the weird table field text placement also when adding data manually for test purposes, though it seems fine when I dump SQL into it.
Thank all of you for your input as always,
fritz