I am not aware of such limit.
You have to be MUCH more specific for us to be able to look into this further. For example:
1. What is the error, verbatim?
2. What is the calculated column definition?
3. What are the datatypes of the underlying column of that definition?
4. What was the registry setting suggestion, verbatim?
Can you post a new database with only this table, and stripped of any PII, to a public location such as a free OneDrive account?
Hello Tom:
I do not have access to the database over the weekend, so here is what I got today when I replicated the process:
1. "The calculated field can not be created.
Verify that expression 'Left([Client Name], 7)' includes fields that exist in the current table."
I would like to state here that it definitely exists. I changed from Client Name to Client_Name to make sure it is not a space issue.
2. Calculated column is simply "Left([Client Name], 7)"
3. Client Name is a "short text" field. I am defining the calculated field to be also "short text".
4. "File sharing lock count exceeded. Increase MaxLocksPerFile registry entry".
Stripping the PII would be a monumental task, at least the way I know how. I will work on it when I get a bit more time. One table has 61K records, another 71K.
In fact, what I am sensing is that I may be forcing the limits of what Access can do. As I said in my initial post, when I reduce the number of rows to about 1,000, Access has no problems in creating
the calculated field.
Thanks for your help,
Al