Clear out data (1 Viewer)

[AccessBlaster]

Okay Guys, lets back off the critique. @DakotaRidge has agreed his project needs to be split. That's a giant step in the right direction. Next step will be normalization. There's hope. I haven't lost faith.

I would normalize first, and try to understand why. Normalizing would cut the number of tables to be moved to the BE.

 

[LarryE]

It would be funny if we are all just being trolled. That seems way more likely than this is real.

Thought the same thing since post #1. Thousands of forms and reports and tables? Not likely, even if ACCESS does allow it.

 

[MajP]

Today, if I send folks 10 tables, 30 forms, and 20 reports to copy into BE and FE files, it won't get done

Yes in your world you could never get any benefit of splitting the db so you are correct there is no need to do so. In everyone else's world they can. In a real db there comes a time were the tables are 98% locked down for changes. You know what data you plan to capture. Now the FE will continue to grow as you create more forms, reports, queries, code and other functionality. You do not send the user forms, reports or anything else to import. You send them a new FE with new/update forms, reports, queries, and code.

Everyone once in a while in the real world you have to update the BE. Hopefully this is extremely rare. This may require them to give back the db so the developer can make changes. Or as a developer you have to make a complex tool to alter the DB and not mess up their data. Or a tool to migrate into the new db.

 

[BlueSpruce]

I would normalize first, and try to understand why. Normalizing would cut the number of tables to be moved to the BE.

Let's take baby steps, one step at a time. I do this all the time with users. The easiest step right now is to split db, so let's now take that step since he agreed it makes sense to do so. Normalization will take much longer to do. It doesn't have to be Domain Key NF, nor 3NF. Second normal form will suffice. Then he can get rid of so many fields, tables, forms, controls, command buttons, etc. etc.

 

[MajP]

The easiest step right now is to split db, so let's now take that step since he agreed it makes sense to do so. Normalization will take much longer to do

There is no benefit in splitting the database. If the tables are changing all the time, what would you gain? How will that simplify anything?

 

[Isaac]

It would be funny if we are all just being trolled. That seems way more likely than this is real.

I was pondering this earlier while getting Taco Bell. There's got to be something he likes out of this (fact #1). Fact #2, the only thing he's getting in response is admonishments to do things differently. Put those 2 facts together.

What does he like from this? Generating a big hullabulloo, is what it seems like.

 

[AccessBlaster]

Until the OP uploads the database or at least a access relationships table view, it's all speculation as to what he's really doing.

 

[BlueSpruce]

I was pondering this earlier while getting Taco Bell. There's got to be something he likes out of this (fact #1). Fact #2, the only thing he's getting in response is admonishments to do things differently. Put those 2 facts together.

What does he like from this? Generating a big hullabulloo, is what it seems like.

Hey, not everyone's an experienced db application developer. There are many many others still using Excel instead of a db to run their biz. How many improperly designed Access apps that were developed by users, and still running for decades do you think are out there?.. MILLIONS!.. I've seen queries and forms for specific date ranges, mimicking excel sheets!

 

[BlueSpruce]

It would be funny if we are all just being trolled. That seems way more likely than this is real.

It feels like that, but trust me, it's real. Remember that not everyone's an experienced developer. How many improperly designed Access apos are out there?

 

[Isaac]

It feels like that, but trust me, it's real. Remember that not everyone's an experienced developer. How many improperly designed Access apos are out there?

I think there is a long reputation of posting like this, that's what we're getting at, it's not just this thread and the refusal to take any advice (which is impressive enough in its sheer magnitude), but a history of posting like this and not changing the mind on anything

 

[BlueSpruce]

I think there is a long reputation of posting like this, that's what we're getting at, it's not just this thread and the refusal to take any advice (which is impressive enough in its sheer magnitude), but a history of posting like this and not changing the mind on anything

I've known @DakotaRidge ~10 years and he's a retired government Geologist with a Ph.D. who's an expert in managing huge gov proposals and contracts. He learned Access on his own and started developing a Proposal Mgmt app with Access that now has thousands of objects and it hit the 2GB limit. He focused on the UI and did not worry about normalization, until now. Sometimes It's hard for ole folks like us to learn new tricks.

 

[NauticalGent]

Proposal Mgmt apo with Access that now has thousands of objects and it hit the 2GB limit

...and yet...

 

[Isaac]

I've known @DakotaRidge ~10 years and he's a retired government Geologist with a Ph.D. who's an expert in managing huge gov proposals and contracts. He learned Access on his own and started developing a Proposal Mgmt apo with Access that now has thousands of objects and it hit the 2GB limit. He focused on the UI and did not worry about normalization, until now. Sometimes It s hard for ole folks like us to learn new tricks.

And yet, he felt the need to reincarnate his old account DenverDB into a new account, which is generally an activity reserved for trolls and not something legit people do

 

[BlueSpruce]

And yet, he felt the need to reincarnate his old account DenverDB into a new account, which is generally an activity reserved for trolls and not something legit people do

I seriously doubt he intentionally did that to troll. He probably forgot he had that old account. My intention is to help him properly design and develop his apps. He has already shown willingness to split his db.

 

[Isaac]

I seriously doubt he intentionally did that to troll. He probably forgot he had that old account. My intention is to help him properly design and develop his apps. He has already shown willingness to split his db.

Anyone can judge for themselves the relative level of 'troll' that this situation is, by searching for DenverDB's old posts. It's a bunch of the same - 1000's of lines of talking about his 1000's of forms with everyone frustrated that he never took any advice.

 

[LarryE]

I've known @DakotaRidge ~10 years and he's a retired government Geologist with a Ph.D. who's an expert in managing huge gov proposals and contracts. He learned Access on his own and started developing a Proposal Mgmt app with Access that now has thousands of objects and it hit the 2GB limit. He focused on the UI and did not worry about normalization, until now. Sometimes It's hard for ole folks like us to learn new tricks.

Then he shouldn't be taken for granite and seems to be getting boulder.

 

[BlueSpruce]

Then he shouldn't be taken for granite and seems to be getting boulder.

He's already agreed to split his db. What if I get him to normalize his db? Whether he does, or not, you always have the option to filter him out.

 

[LarryE]

He's already agreed to split his db. What if I get him to normalize his db? Whether he does, or not, you always have the option to filter him out.

Geologist taken for granite and getting boulder....

 

[isladogs]

Okay Guys, let’s back off the critique. @DakotaRidge has agreed his project needs to be split. That's a giant step in the right direction. Next step will be normalization. There's hope. I haven't lost faith.

I disagree. Nowhere in this thread has he agreed to split his database.
We had the same interminable discussions with his proposals database. It never got implemented and indeed never went to production.
I very much doubt this will be any different. This database will likely remain for his personal use only

David is a nice guy. However, he is a master at stringing people along knowing everyone wants to help him, but having no intention of ever changing his approach.

 

[DakotaRidge]

Yesterday was an interesting and very good day for me. I went to the library with two of my grandsons where I read the current edition of the Kiplinger Personal Financial magazine. I found an article with a map showing states with no state tax. The article allowed me to create a new map in my Personal Finance and Health database.

Later in the day, I found a map prepared by the CDC that shows states with increasing incidences of Covid this summer. So, I created another map in my database. The CDC suggests ways that folks can address their exposure to new strains of Covid.

Then later in the day a professional troll hunter targeted me. He had discovered that I had had another AW account in the past. That’s true. I created a new account a few weeks ago when UtterAccess closed down shop. My old PC died in December, and I lost my AW password so I could not get into AW to ask questions of Access experts. I figured that as long as I was using only one AW account that it was okay. Who knew a troll hunter would come along and research my activity back several years.

I also had two UA accounts because the UA administrator had a problem with my first account, and he decided to create a new one for me.

Now my database has 556 forms, which the troll hunter thinks is excessive. I am sorry that I read a lot, and when I find useful ideas in the literature, I add new tables, forms, and reports to my database. My goal is to end 2025 with a thousand forms, and equal numbers of reports and tables.

After adding new forms today, I reconfigured three of my custom navigation forms. I repositioned the command buttons that open forms that list Covid symptoms and symptoms of illnesses related to contaminated water in public pools.