Simplifying data entry, but UserForms gives memory error message. Other solutions?

Hi and welcome to the forum.

It would be easier to help if you could attach the file rather than pics of it.

BSB

Good point, and thanks for your willingness to help! I've attached the file here. This is a new workbook that's an attempt to consolidate multiple old versions. I was still in the process of building the userform when I started getting the memory error. I assume it's because there are too many items in the userform. So far this isn't even close to operational, but is a work in progress. Eventually, it will have other sheets, for different teams, and will have a summary sheet doing weighted/total calculations.

Maybe a userform isn't the solution in this case, but I am open to other possibilities. Many of the end users that will be doing data entry are not skilled in excel, so having such a large spreadsheet is intimidating for them- and leads to entry errors.

That's a LOT of controls on one userform!!! And I think that's the issue here. Search for this issue on Google (other search engines are available! ) and you'll read a lot of differing opinions on why this happens.
Building userforms is a big part of what I do for a living and I've run into this issue many times when being over adventurous with the controls in the past.

If you HAVE to use Excel for this (i.e. you cannot use an actual database / DBMS) then the trick is splitting one big userform down into several smaller userforms.

If your current userform is for data entry only then do you need all those controls is the question you should be asking yourself.

Here's a few more:
- Does the user need to see all those previous month's worth of data on the form at once?
- Could they get away with a shorter view, say 3 or 6 months previous, and still work effectively?
- Do they need all the future months visible on the userform if they're only to be updating a short way into the future?
- Would multi-column listboxes work to mitigate the need for all those textboxes for previous months?

If I were the developer on this there are MANY more questioins I would ask, but I shall leave it at that for now.

I'm sure Excel COULD manage this task if it were designed efficiently. But to say for sure I'd need to know a WHOLE lot more about the project in hand and you may need to head down the path of a developer to do the work for you.

BSB

Thanks BSB,

I was guessing that was the problem. Thanks for the other suggestions! The month system we use for entry is strange, but it saves a lot of time later for calculations. I think it would be possible to split into smaller userforms though. I appreciate the advice- at least this way I don't waste time trying to build something that can't run.

Even though I've gotten some good advice, I am open to any other feedback from this forum.