Anything is possible
were any of the "changes" to these fields or layouts ?
what if you add the fields again to the layout?
are the calendar drop downs checked to "show and hide" ? that sometimes helps
> I opened a copy of this file, without the latest changes (I built the file, and I made the changes) from 8 months ago, and this issue is not there. I've restarted my development box
One layout with problem, no changes. Parts of that layout copied and pasted to the other layout with the issues. Both layouts have the same issues.
That said, I created a new layout, and rebuilt it from scratch, no copy/paste. That layout also had the same issue.
This would lead me to believe, if it's corruption, it's not to the layout.
I've tried both show and hide for the drop downs.
"The problem I'm seeing now: I can enter a new date once or twice in either of the fields, and then I can't enter a date until I leave the layout and use a script to come back in (this script sets the ending date to today, and the beginning date to 7 days earlier (as a default when hitting the layout). "
I suggest that you let someone check the file. Sometimes 'other eyes' can spot something. You can PM me and I will provide my email for sending the file if you wish to keep it more private. There is one bug which might be involved ... it has to do with field in header being unenterable if the current record is not in view at the time.
I would look for other possibilities to the issue before assuming corruption ... this just doesn't feel like corruption to me. I, and I'm sure others will help. :-)
Also, have you ran the 11.0v4 updater for Mac?
it has to do with field in header being unenterable if the current record is not in view at the time.
I've seen this with Non-global fields, but not with globals. Can you please explain this bug?
It is a long thread which starts in version 10 and rolls into version 11. I haven't tested it yet in 12.
I am not sure this is your issue ... only that we should explore further.
LaRetta, this is a great find. I read the thread, and will play around with it later today. I'll post my results.
LaRetta (and others)
Again I thank you for pointing me to that thread. The fix for me was Go to first record at the end of the script. Works like a champ!