Hi,
No, I typically use more advanced logic for determining editability based on fields such as date, status etc... Without the ability to control record level editability or more particularly field level editability within editable queries, the only solution is to eliminate any records or fields from that query that you don't want to have changed on you.
This is a shame because if you could control the editability at a field level only for a given query, the editable queries could become a true workhorse. As it is, I would need to have the user jump out to non-editable form versions of the record (largely using html cells) to allow the user to see all of the relevant fields within the record and control which ones they could edit on that particular form, thus defeating the benefit of the editable queries.
I often find that I have situations where a user with limited access rights is allowed to create a record but only allowed to edit certain fields within that record after the record has reached a certain status level. I realize that there are always workarounds and access levels are only one way to control editability, I am speaking specifically about the new editable queries and how they could be made exponentially more usefull in real world situations that we run across on a daily basis.
Anyway, please treat it only as a suggestion and something to think about. It you feel it might be possible yet, not a high priority please pm me and let me know whether there might be an opportunity for me to fund the change.
Cheers,
Pete
