What you describe isn't something that I've seen or heard off. What more can you tell us?
Any script triggers set on the field?
When this problem happens, have the users click a blank area of the layout (which commits records) and see if that helps any better than clicking on different other fields.
Try recovering the file and test the recovered file to see if it shows the same issue.
I think the commenting system automatically assigns an "assumed answered" tag to any post that hasn't had any action in a month, to keep open questions from just piling up.
Post is only two days old...
Original post was Dec. 2, 2016, and the next action on this page was Mike's question on Jan. 4, 2017, at which time the "assumed answered" tag had already been applied.
sigh, morning caffeine hasn't kicked in yet...
Yes. I have asked this question several times and have a problem with the
Community web site in that it is not obvious how to mark my previous
questions as answered. I have gotten a lot of answers from previous people
and I really appreciate that. Your tips on scripting will really help me
since I am not an in-depth scripter yet. This will allow me to write a few
scripts that can accomplish the same task while looking at different value
list tables (I have 14).
My wife keeps telling me about this revolutionary caffeine substitute that's apparently widely available, so I can't imagine why I haven't heard of it before. She calls it "sheep" or "sleep" or something like that.
Richard S. Russell wrote:
She calls it "sheep" or "sleep" or something like that.
Wake up, sleeple?
it is not obvious how to mark my previous questions as answered.
You have to make your "discussion" a "question" when you make your first post to ask the question. Then you get an option that allows you to mark a response as "answered".
I'm pretty sure that this last one was a question so I'll go out and mark it
"Answered" since my script just performed what I wanted.