First of all, loading 42 subforms of the access form is very fast, and in fact I do it for years and years, and the loading time of 42 subforms is actually instant.
Thus, this suggests that readers may ignore some comments here, suggesting that script-based or text-based systems, such as HTML, will somehow work faster inside some browser rendering system than a desktop application high-performance Windows that has the direct ability to directly record a graphics card.
Remember that if you have simple and basic knowledge that Windows desktop applications can write directly directly to video cards, few will try to compare and assume that the rendering system in HTML has a real hope of comparison in terms of speeds if we go to compare two different architectures here.
So, the real problem is how quickly you can make a calendar calendar, and will 42 subforms be a problem?
The answer is that 42 subforms are not a problem and are FAST!
The next instant access to my resource is displayed instantly.
The aforementioned mine access calendar has been used for many years, even under production conditions. Even if calendars have every day with ADDITIONAL data that cannot fit on the screen, it starts at boot time. A good number of them work, in which the desktop (client) gets into the backend of the SQL OVER STANDARD INTERNET server with the hosted version of the SQL server running on the website. And even in this case with limited bandwidth, the download time and calendar response are close to instant. Thus, performance is no problem, even though I am using accDB (file-based) back-end, using SQL server for the back, and even more amazing, and as already noted, this form works well with many of my clients working with this OVER access calendar are regular Internet connections in which the back end is an SQL server running on a hosted website. And I even have a version working with the end of SharePoint (list), and again it works without problems and there is a noticeable delay.
The above design has 42 subforms, and, as noted without data, subformats load absolutely instantly. It is important to indicate this, and therefore I presented some real facts and factual data in order to humiliate other comments made here by those who clearly do not understand and do not understand the basic computer architecture. These people, therefore, suggest that loading 42 subforms somehow arises in terms of slowing down the software, when in fact I can easily demonstrate that this is not the case. Thus, the testimony of witnesses and the testimonies of others here may be unfounded, and therefore this point of view is based on the LACK understanding of how basic computer operations work in our industry. HTML cannot hope to compare with such a setting here.
And speaking of web based now that Access allows web publishing, I am posting the next video from a Calendar created in Access that runs in a web browser. This browser-based browser was built ONLY using Access and without any third-party tools.
http://www.youtube.com/watch?v=AU4mH0jPntI
As a result of the above video, the BUTTER SMOOTH version and the instantly responsive web version of this Calendar application are displayed.
Now I have to point out that in the above example on the website I do not use 42 subforms, since in the web browser each form is a separate frame and causes the form to be rendered again from the server. This means there is no answer for the Access website based on 42 sub-forms. You will get huge success in terms of rendering (even if there is no data, since the XMAL form does not load on demand to save time, but in this case this setting hurts).
However, as shown in the video, the solution for the website (as well as for working on the basis of the client) was supposed to populate the table into which you bind the text fields to this table. Thus, the presence of a single recording display, as noted and shown in the video above, shows that such a result means an almost instant response and as noted even in a web browser.
I emphasize the WEB-based application in that the video was only created using Access and other tools.
Now back to the performance issues and client application. The problem, of course, when we NOW KNOW that loading 42 subforms is not a problem.
Of course, the problem is that in SQL queries 42 separate SQL queries with all kinds of expressions, in order to extract data into these subforms, there is a bottleneck and slow performance. Thus, the performance issue will NOT change if we use 42 text fields or even 42 lists.
So the problem is trying to execute 42 separate SQL queries. Keep in mind that each SQL query takes time to parse, time for syntax checking, and then query plans, etc. In fact, a fairly large number of actions must occur before the data even begins to flow for one given request. In fact, I find that a single request can cost about 10,000 lines of data flow in terms of bandwidth.
Based on the above information, the reason why my project of my 42 such subcategories can be downloaded and executed instantly is due to the fact that I perform ONLY ONE QUESTION to return data for the whole month. In other words, I am executing a query with a start date and an end date. Then I run the VBA code to process the data from the resulting reocrdset in subparagraph 1 to 42. Thus, the VBA code fills the resultant recordset data into 42 subforms. Thus, this is the key concept and proposal here to ensure high performance computing and no slowdown.
So, in conclusion and conclusion:
The performance drawback is not the use of 42 auxiliary forms, but the presence of 42 sets of records and 42 queries, and potentially additional code and expressions should be evaluated 42 times. Eliminate 42 queries and 42 times, and RE will execute such SQL queries, and this bottleneck will largely evaporate.
I dare to argue that using 42 lists or even a total of 42 text fields and executing 42 such SQL statements will not bring any significant performance improvements.