Well, this is my first post in this forum.
I have a medium complex database, in Access 2019, with more than 100 tables, a lot of relationships and, of course, a large set of forms and reports.
Those forms and reports often uses the same fields from the same tables.
Just as a sample, I have a person Table with a PersonalID fields, defined by the Italian Departmen of Finance. Each citizen has exactly one.
It must follow this pattern(in Access): AAAAAA00A00A000A with a length of exactly 16.
And, if it conformed to the pattern, there is a microservice to validate it with the Finance Department: correct or not correct.
Well, I would like to show an incorrect PersonalID fields in red, wherever it is used, defining just once this conditional formatting.
AFAIK, at the moment I need to rewrite the conditional formatting rule every time I use the field in a form and in a report. And I cannot define it for a table view.
This is not only annoying, but also prone of mainteinance errors.
Is there anyone that has an idea on how to solve the problem or to find a workaround for it?
TIA
Paolo
I have a medium complex database, in Access 2019, with more than 100 tables, a lot of relationships and, of course, a large set of forms and reports.
Those forms and reports often uses the same fields from the same tables.
Just as a sample, I have a person Table with a PersonalID fields, defined by the Italian Departmen of Finance. Each citizen has exactly one.
It must follow this pattern(in Access): AAAAAA00A00A000A with a length of exactly 16.
And, if it conformed to the pattern, there is a microservice to validate it with the Finance Department: correct or not correct.
Well, I would like to show an incorrect PersonalID fields in red, wherever it is used, defining just once this conditional formatting.
AFAIK, at the moment I need to rewrite the conditional formatting rule every time I use the field in a form and in a report. And I cannot define it for a table view.
This is not only annoying, but also prone of mainteinance errors.
Is there anyone that has an idea on how to solve the problem or to find a workaround for it?
TIA
Paolo