The reason for so many userforms ... this is not one application. The main application relies of upwards of 3 different workbooks that hold dynamic data day by day. Each workbook has its own set of forms that allow users to access and manipulate data unique to that database. This allows data to be worked on by users without tieing up access to the others. I can have users working on each database independently at the same time. With one workbook and with one userform, I can't allow multiple users to work with their assigned data.
The main application ties all these unique and sometimes independent workbooks together. This master application, I am trying anyway, has access to the other workbooks userforms so that data can be accessed and manipulated from within.
For example, one large database (workbook) is comprised of customer information. It has it's own forms unique to entering and manipulating data specific to customer information. Another workbook holds information specific to facility rentals and has no reliance on the customer data. It has it's unique forms. I can have two users working on each of these workbooks at the same time, whereas if it was one workbook, only one could be working on it at any given time.
A third, and master application, ties the data from both the customer data and the facility rental data workbooks to create a specific document. There are times when working with this main application, data from the other workbooks is missing or incomplete as identified by the application. (eg encounters a missing customer record) When this happens, the idea is to be able to access that specific workbook's (customer) forms (using base data from the main application) to edit/enter that information. If the main application encounters missing data related to the customer, the user of the main application can edit this information throuhgh the customer workbook with the same userform that one would use when working with the customer workbook independently. It simply saves me having to recreate the same userform in the main application. The missing data is then maintained in the customer workbook, and made available in the master application as a result.
Yes ... the data is interdependent, and I'm trying to establish access to all through one master application without having to recreate userforms. The databases are fairly large, so trying to maintain them all in one workbook makes for a large slow file, as well as removes the ability to work on different databases independently.
I think the easiest solution is to assign the value to a cell and access the cell rather than the object.