11/08/2025
A bit of ancient history.
Way back in '97, Mike had developed a website for a client, and had a lot of personal experience in programming. He hadn't yet done it as a job, except that one website.
He got hired as a temp employee doing data entry in the "New Media" department at LM Berry Company in Dayton, OH.
The Berry Company was one of the largest publishers of Yellow Pages, and the "New Media" department would later evolve into the Online Yellow Pages.
The data entry job was tedious and error-prone. There were several markets, each with its own template. The templates were all very similar, but each market had its own fields.
They would open the plaintext template file, which was HTML, search for strings of "###X" (the fields) and replace those with the information that was supposed to be there.
Inevitably, when they switched markets, they forgot to fill in one or more fields that was different from the previous template they'd worked on.
While the job was tedious, Mike liked the people he was working with. The manager, Barry Sanders (not the one who played pro football), came to Mike and said, "After Thanksgiving break, we'll only need you for a couple more weeks."
Mike took one of those template files home and, over that long Thanksgiving weekend, put together an Access database with forms. It would save the data entered and generate the full HTML that could be uploaded to the server. If implemented, it would mean no more searching for fields or dealing directly with the HTML in the template. It would mean fewer errors, a better data entry experience, and a *lot* more productivity.
On Monday, he took that Access database in and showed it to Barry, who got *very* excited. He said, "If you can do *that*, maybe you can do *this*."
He'd been kicking around an idea in his head for a while that was basically what Mike had done, but it would be a web interface the data entry operators could use. Everything would be stored on the server, so there'd be no upload, and the HTML files would be output by the server-side application.
At the time, Mike's go-to programming tool was Visual Basic 5. He wasn't sure he could build what Barry envisioned, but he was confident he could figure it out, so he said, "Yes. I can build that."
Due to his budget, Barry couldn't hire Mike directly, but he *could* hire a contracting company.
So, CastoWare was born. Mike wrote that app in VB5 with an Access database and put the executable onto their intranet web server as a CGI. It produced the web forms for the data entry operators, stored the data, and generated the HTML pages on the public site for their advertisers.
Jack Poe, a graphic designer for Berry, designed the appearance of the pages.
In '98, that app won an award from the company. Jack & Mike were listed as the developers. That was the start of Mike's actual career as a web developer and the birth of CastoWare Development.