Multiple instances of same form...

QMDirk

Member
Local time
Today, 15:05
Joined
Nov 16, 2019
Messages
52
I've heard about 'cascading' forms, or subforms, but what I need to do is open the same form twice or more times, on the same terminal, where each instance of the form inputs data for a different production line but still stored in the same table, and any instance can be closed without closing any other instance. Does anyone know if that is possible? Thanks.
 
Thanks! I'll check it out now.
 
Here is a simple demo. Just keep selecting employees from the combo after one opens (have to move them out of the way). You can even select the same employee multiple times.
However, you need to manage the collection as shown in the link from DBGuy.
 

Attachments

My work has 7 production lines, canning cooking sprays. On each line there are 7-9 positions that fill out a form for each product produced. For lack of knowing a better way, I made a separate form for each position, each form being linked to separate subtable to store the data. I created so many tables because, with the high volume of cans we produce, I didn't want to max-out my table with too much data. So, in all, my program has something like 80 forms, and even more tables. Is this a recipe for disaster? the file size is only up to somewhere around 92Mb so far.
 
My work has 7 production lines, canning cooking sprays. On each line there are 7-9 positions that fill out a form for each product produced. For lack of knowing a better way, I made a separate form for each position, each form being linked to separate subtable to store the data. I created so many tables because, with the high volume of cans we produce, I didn't want to max-out my table with too much data. So, in all, my program has something like 80 forms, and even more tables. Is this a recipe for disaster? the file size is only up to somewhere around 92Mb so far.
Hi. "Maxing out" an Access database usually only concerns its file size. If you only had one table with millions of records, as long as the file size is not close to the limit of 2GB, then Access should be able to handle that one table with millions of records. However, if you divide those millions of records into multiple tables, then you add some "overhead" to the file size for keeping track of all those other objects. So, if all the data are the same anyway, it might be better to keep them in one table and not worry so much about how many records are in it. Just my 2 cents...
 
Here is a simple demo. Just keep selecting employees from the combo after one opens (have to move them out of the way). You can even select the same employee multiple times.
However, you need to manage the collection as shown in the link from DBGuy.
Thanks @MajP Your example reminded me of something I had forgotten about for a few years in my project system Which i put down to some move code but after looking at your example I saw I had done this Dim frm As Form instead of Dim frm As Form_frmRemindersPopup Could have kicked myself more for forgetting about it rather than when I originally wrote the code just goes to show books arn't always right as did it from an example.

thanks Mick
 

Users who are viewing this thread

Back
Top Bottom