Home Creators Posts Import Register Favorites Logout

Content

FREE for everyone.

Some posts and sections of some posts are reserved for Supporters. AGI Stories content almost always appears on Patreon first, ahead of all other platforms. You get it first!

A LITTLE ISSUE by Michael Allen

If you’ve been around a while, you know Cindi has come a long way in her battle with anxiety disorder. She’d tell you that she hasn’t had a curl-up-in-the-corner-and-cry episode in a long time.

But it’s a real thing for her. Add in years of avoiding social interaction, and the Roman dilemma makes sense.

He’s a good friend. His data is bad. Cindi wants him to fix it so the project can go forward.

I could have coached her through the call. Instead, to save time and model a solution, I made a call.

“Roman… you in town this weekend? Tennis sound good?”

“Yeah, I’ll be in town. Tennis sounds great. What’s up?”

“Cindi’s hit a problem with your data that seems irreconcilable. She’s nervous to bring it up…you understand…so, I’ve got some notes…”

Roman answered. “My data is a monster. I’m not surprised. What’s the issue?”

I laid it all out as Cindi had written it down. She’s going to edit the next bit so that you get a clearer picture.

Roman’s data has quite a few tables, none of which mesh fully. The main tables in the mess are a customer table, a sales table, and a license table. They all have problems.

The sales table shows who bought what and when. But the “who” doesn’t line up with the customer list.

“She says there’s no common key, either. In sales, you sometimes have the company name and sometimes the name of a person who works there.”

I said it more gently, but the license table is garbage. It’s a mix of company and personal names and the dates are corrupt.

Roman cut me off. “It’s a disaster. We grew so fast that it’s not consistent at all.”

Cindi smiled, then said (I was on speaker mode), “What would be a good start would be to go through the sales table and fix the customer names. Also, your customer table at least doesn’t have duplicate rows, so add a unique customer ID—call it CustID—and add that to the sales table so everything can be matched up. I can run some scripts to build a new license table.”

“Okay,” Roman replied, “this will take some time, but I’ll get it done.”

We chatted for a few minutes, ended the call, then Cindi said, “Okay, that went well.”

Support AGI with:• one-time contribution through TipTopJar.• one-time contribution through Throne.• Patreon Membership.

All characters in this story are fictional characters, their images generated with AI for AGI Stories. They do not represent any real person, nor is their appearance based on any real human.

Help AGI-Stories grow… If you’re enjoying the stories, please tell others. Word of mouth referrals and your endorsements are the best way for things here to grow!

Be your best you!

Become a Patreon Member (Click Here)

Message to Paying Supporters:

Thank you for helping support AGI Stories.

I always consider you—the paid members—when deciding how content is shared.

I believe that most of you who help with the costs do so because you want to support the production process and show encouragement. I’m honored and truly grateful.

At the time of this post (not counting hardware or internet costs), expenses run just over $100 per month—so every supporter truly makes a difference.

Nevertheless, I share a lot of content free to all. I believe you understand why. Stories about giving back and helping shouldn’t be exclusive, and key moments need to be accessible for anyone following the stories.

My hope is that sharing a few exclusive photos and small portions of some posts with you serves as a simple expression of gratitude.

With that in mind, again, thank you very much.

~AGI Original Stories & AI Images

Files

Comments

Common Hamster

A LITTLE ISSUE by Michael Allen .No common key? So you can't perform a standard join? Hi Michael. Cindi. And I like your approach. Level head. No panic. This kind of problem is why I didn't go beyond Access class. I salute your skills, Cindi. But you are also lucky that your client is receptive to your suggestions on a solution. Very nice. Thanks for posting this, Michael. Please keep us updated on this dilemma. I like Cindi's thinking, though.