EdwardMartinIII
Technical User
I have a project I'm working on.
At the moment, I have to use Excel, so I recognize that I might have to use a Stupid Solution. I'll say that up front.
I have a big page full of controls. One of them is "How many widgets?"
This is the requested action when that control is clicked (gotfocus):
1. Open a Userform which queries for "How many widgets (1-50):"
2. Using that number, then activates another set of controls on the same form that allows you to page through all x widgets. For each widget, we want you to specify certain things about it. Some is wild text, others are from dropdown.
3. All of this information must be saved somewhere in the speadsheet such that it can be programmatically retrieved by other parts of the spreadsheet/the internal VBA app, for other calculations.
I'll say up front it's not actually physical widgets, so that's just an example.
Example: I pick 5 widgets. I'm then faced with an interface that for each of the 5 widgets, I'm asked:
1. How much does it cost?" free text/integer
2. What department does it belong in? (dropdown1)
3. Which manager is in charge of its inventory (dropdown2)
I already have a secondary sheet with lookup tables, so the various dropdowns can be populated from those.
A requested action is "I want the program to be able to determine if, for example, ANY of the widgets are in Department x or if any of the widgets are overseen by Supervisor y and so forth."
Now me, I'm thinking "Could you come up with a BETTER use for a database?!" but the whole thing is already a big Excel spreadsheet and I am being STRONGLY encouraged to keep it there. If I want to move it to a database with a pretty face, I'm going to have to be REALLY persuasive, because that'll take the project down for a while during the conversion.
So, is this a thing that is reasonable to ask Excel to do?
Edward ![[monkey] [monkey] [monkey]](/data/assets/smilies/monkey.gif)
"Cut a hole in the door. Hang a flap. Criminy, why didn't I think of this earlier?!" -- inventor of the cat door
At the moment, I have to use Excel, so I recognize that I might have to use a Stupid Solution. I'll say that up front.
I have a big page full of controls. One of them is "How many widgets?"
This is the requested action when that control is clicked (gotfocus):
1. Open a Userform which queries for "How many widgets (1-50):"
2. Using that number, then activates another set of controls on the same form that allows you to page through all x widgets. For each widget, we want you to specify certain things about it. Some is wild text, others are from dropdown.
3. All of this information must be saved somewhere in the speadsheet such that it can be programmatically retrieved by other parts of the spreadsheet/the internal VBA app, for other calculations.
I'll say up front it's not actually physical widgets, so that's just an example.
Example: I pick 5 widgets. I'm then faced with an interface that for each of the 5 widgets, I'm asked:
1. How much does it cost?" free text/integer
2. What department does it belong in? (dropdown1)
3. Which manager is in charge of its inventory (dropdown2)
I already have a secondary sheet with lookup tables, so the various dropdowns can be populated from those.
A requested action is "I want the program to be able to determine if, for example, ANY of the widgets are in Department x or if any of the widgets are overseen by Supervisor y and so forth."
Now me, I'm thinking "Could you come up with a BETTER use for a database?!" but the whole thing is already a big Excel spreadsheet and I am being STRONGLY encouraged to keep it there. If I want to move it to a database with a pretty face, I'm going to have to be REALLY persuasive, because that'll take the project down for a while during the conversion.
So, is this a thing that is reasonable to ask Excel to do?
![[monkey] [monkey] [monkey]](/data/assets/smilies/monkey.gif)
![[monkey] [monkey] [monkey]](/data/assets/smilies/monkey.gif)
"Cut a hole in the door. Hang a flap. Criminy, why didn't I think of this earlier?!" -- inventor of the cat door