Hi The_Doc_man,At least partly serious. It has been my experience that when theory collides with reality, it isn't always pretty. In a development environment that has finite capacity, headaches seem inevitable. Therefore, I'm questioning how many times you have had to modify your magnum opus?
I like your "partly"
It is good to know the limits. I don't see Access to rule the world, and see it only as a small scale application. Of course you can argue what small scale is.
I am not commercial. I develop applications for all kind of non profit organizations driven by volunteers, that don't have the budget to buy commercial software, or even to pay the annual contributions to Microsoft. For that reason I develop in A2007.
"Magnum opus". You may write it in capitals.
If have modified it as many times as there are days between Access2.0 and today.
These modifications because of headaches, or capacity, but because of improved functionality.
It is the result of many, many steps of generalization, a real evolutionary path.
Capacity is not the problem. If there are specialized functions that need much data, like postal codes, I have a specialized postal code application. The code is almost at its end of generalization, and has practical no limit.
My shared library database, that contains all generalized code, is today 55 Mb. When will I ever reach a limit with it?
Imb.