Be aware there is a much, much greater chance of corruption due to the constant creating and deleting of objects.There will be also be bloat........
Be aware there is a much, much greater chance of corruption due to the constant creating and deleting of objects.There will be also be bloat........
Yes I agree. I am actually recoding a VB.Net program into Access - I know this is very retrograde and I have reasons to do this (too long to explain). The VB.NET does the job with a GridView - which isn't the neatest of implementations but it does work for the purpose I have in mind. Now if Access supported a GridView......
BTW, there is a control limit on a form (unless that restriction has been deprecated). What can you do with a data grid that you can't do with continuous subforms?
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
I want something that looks like a calendar, simple squares reading left to right then start the next row... Only thing in each square is a simple small bit of text. With subforms (I think) I would have to line them up across the frame and populate the top entry in each then move down an entry as I get the next batch of numbers etc.... (Of course I am a bit of an Access novice, so I might be misunderstanding subforms)
I take it that the 'something' isn't a calendar as that would be easier than what you seem to be doing. If you had an example of what it will end up looking like, you might get ideas. "as I get the next batch of numbers" sort of suggests that you're creating controls on the fly based on the number of fields x records. That doesn't sound manageable nor like the correct approach. Maybe Albert's images and advice will provide some insight
https://answers.microsoft.com/en-us/...d-7fd4efd3ea81
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Perhaps you could show a screen shot regarding
There may be options.The VB.NET does the job with a GridView - which isn't the neatest of implementations but it does work for the purpose I have in mind. Now if Access supported a GridView......