Clear out data (1 Viewer)

One of the main issues I see is a rush to the end product, reports filled with flashy animations and eye candy while completely disregarding the foundational skills needed to create these advanced features, such as VBA.
 
From what I have seen, there is 1 and only one! You are looking at it.
I have seen thousands of examples on this forum and other forums of inefficient designs. I have never thing anything even 1/100th of the purported scale of inefficiency.

Everything else I have ever seen, you could help the OP take a dozen forms, queries, or tables and consolidate. Or normalize the data and knock it down from 10 tables to 3. There is only one person in the world who has hundreds/thousands of objects to do something that could be done in 1/100th of that.
@DakotaRidge's rationale is to provide his users with hardwired forms, customized for a single specific purpose, e.g. a form for food bought at Wamart, another form for recalled food, another form for recalled medications, and so on. He doesn't want a generic form for all cases, all vendors, all item categories because he thinks his end users are going to get confused selecting values from cascading combo boxes. Those require vba code and he doesn't do code, so he relies on limited macros and hardwired forms as a workaround because that's all he knows how to work with. Same reason he uses mvf's, because users can select multiple values from one dropdown list. He prioritizes the UI and UX not knowing he can merge all those hardwired forms and use parameterized queries that leverage normalized tables. He wants to provide for all possible use case scenarios, so that combined with his hardwired forms yields thousands of tables, hardcoded queries, and so forth. go figure... I have seen other people's apps designed like this, including his proposals mgmt app that surpassed 2GB quite a while ago. I cannot visualize how long it would take for me to bloat a db to 2GB. I guess it can happen quickly if you embed images in 4,000+ forms, but just building that many forms would take me an eternity! How does one efficiently navigate to a specific form with so many of them? Stacked submenus? Treeview menus? There are very few valid reasons for building denormalized apps. A Decision Support System performs better with denormalized aggregate tables, and some normalized apps that have too many joined tables that requires hairy stacked queries, so you partially denormalize some data to improve performance and simplify queries.
 
A Decision Support System performs better with denormalized aggregate tables, and some normalized apps that have too many joined tables that requires hairy stacked queries, so you partially denormalize some data to improve performance and simplify queries.
When he gets to the point where he has an entire data warehouse built that warrants ETL jobs loading denormalized data for reporting purposes, he is welcome to let us know. That's about where it's appropriate.
 
Richard Rost has embarked on a very impressive project that is similar to what DakotaRidge is attempting to do.

He calls it the Fitness Database but it is so much more. A shame he took his toys and went home.
 
Richard Rost has embarked on a very impressive project that is similar to what DakotaRidge is attempting to do.

He calls it the Fitness Database but it is so much more. A shame he took his toys and went home.
I'm sure Richard's not using MVF's and denormalized design.
 
I say have one form for every letter in the alphabet, then try to programmatically line up the forms onscreen to make words when needed! yah, that's what i say, dodgammit
 
It really is a cradle to grave, step-by-step tutorial on apllication development. Over 30 videos and counting
 

Users who are viewing this thread

Back
Top Bottom