Access 2003 in a 2021 World???
-
It's one thing writing a completely bespoke system, but who is going to design this for you? Sitting down a Production Manager (for example) with a blank piece of paper and asking what he wants is a recipe for disaster. Even if they had any idea what they wanted. A Production Manager might roughly know what an MRP routine does, but very few could actually design one from the ground up. It's an extremely complicated algorithm.
-
@Carnival-Boy I agree, which is why most organizations would first look to purchase a stock system that meets most of the businesses needs, and then customize that 1-20% that they need for their business work flows.
Building a piece of software to work the way each and every organization wants is insane.
Imagine if Adobe Creative Cloud did this, nothing would be the same on any given piece of software.
-
Tryton
Use a Tryton partner as your developer. Something happens to that company you can use another one for modifications.The only trick is getting. A Business Analyst that understands the business and can communicate the requirements.
-
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
-
@Dashrender Yeah I'm not going to really take that bet, its the argument that when Access was "King" there were few actual software packages that did what these company needed.
I'd be willing to bet that some developer saw all of these individual MS Access systems and said to themselves I'm going to make one that does all of that without the complexity and came up with Quickbooks.
LOL
-
@DustinB3403 said in Access 2003 in a 2021 World???:
@Dashrender Yeah I'm not going to really take that bet, its the argument that when Access was "King" there were few actual software packages that did what these company needed.
Oh, but we know that's not true at all - it MIGHT be true to say - no one made "simple" end-user creatable software packages that were cheap and that companies were willing to buy, but that's light years away from the best solution for the job.
I know people who use TONS of xls sheets because it's what they learned first and never bothered to look for the right/better solution for their long term uses. There's also the likeliness that the company didn't want to spend tons of money on bespoke software or even a software package that could do it - both with high price tags... only caring about short term gains, not long term business.
-
@DustinB3403 said in Access 2003 in a 2021 World???:
I'd be willing to bet that some developer saw all of these individual MS Access systems and said to themselves I'm going to make one that does all of that without the complexity and came up with Quickbooks.
LOL
LOL agreed!
-
@Dashrender said in Access 2003 in a 2021 World???:
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
It wasn't Access itself that was the thing. It was the JET database engine that Access used under the hood that made it popular.
Back in the 90's if you wanted a simple database in your application and you used something like Visual Basic 3.0 then the JET engine was the first option to consider because Microsoft bundled it with VB and it was free. That's how it gained a foothold.
The JET engine was very very far from the best or even good. It was common to corrupt the database and run tools to "repair" it. But it was available without any effort - today we know that is perhaps the most important "feature"...
If you wanted the best you'd connect your application to an Oracle db.
MS Access itself was never a serious tool that developers used for business applications. It's very limited so VB was the default choice in the MS ecosystem for these kinds of applications.
-
@Carnival-Boy said in Access 2003 in a 2021 World???:
At least with major ERP systems like Microsoft, Oracle or SAP you have a partner network to work with. So if you fall out with your partner, or they put up their fees unreasonably, or they go out of business, then you can simply move to another partner and carry on. That's much, much harder with bespoke software.
That's true, for sure. Unless the original vendor is the source of the high fees, goes out of business (unlikely with the ones you mentioned, but industry ones do all of the time) or if there aren't many partners (a problem we've run into.)
Even good partner fees are often around $250/hr. You can hire a lot of your own staff for that kind of money.
-
@Pete-S said in Access 2003 in a 2021 World???:
@Dashrender said in Access 2003 in a 2021 World???:
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
It wasn't Access itself that was the thing. It was the JET database engine that Access used under the hood that made it popular.
Back in the 90's if you wanted a simple database in your application and you used something like Visual Basic 3.0 then the JET engine was the first option to consider because Microsoft bundled it with VB and it was free. That's how it gained a foothold.
The JET engine was very very far from the best or even good. It was common to corrupt the database and run tools to "repair" it. But it was available without any effort - today we know that is perhaps the most important "feature"...
If you wanted the best you'd connect your application to an Oracle db.
MS Access itself was never a serious tool that developers used for business applications. It's very limited so VB was the default choice in the MS ecosystem for these kinds of applications.
Once Access could use SQL Server, it became worlds better. But the whole "GUI application interface" made it so expensive and limiting that it could never really be a great tool, even when it was a good enough tool.
I've got customers who have built way too much on it and even though they are tiny and use it about as well as anyone could, it's really clear that if they put a little effort into a PHP developer that they could replace everything in a week with something vastly better.
-
@Dashrender said in Access 2003 in a 2021 World???:
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
The primary alternative to Access was always "build something yourself." When Access was "king", VB4 was solid and able to do so much more for less, but in the same style (Windows Forms, JetDB.)
-
@scottalanmiller said in Access 2003 in a 2021 World???:
@Pete-S said in Access 2003 in a 2021 World???:
@Dashrender said in Access 2003 in a 2021 World???:
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
It wasn't Access itself that was the thing. It was the JET database engine that Access used under the hood that made it popular.
Back in the 90's if you wanted a simple database in your application and you used something like Visual Basic 3.0 then the JET engine was the first option to consider because Microsoft bundled it with VB and it was free. That's how it gained a foothold.
The JET engine was very very far from the best or even good. It was common to corrupt the database and run tools to "repair" it. But it was available without any effort - today we know that is perhaps the most important "feature"...
If you wanted the best you'd connect your application to an Oracle db.
MS Access itself was never a serious tool that developers used for business applications. It's very limited so VB was the default choice in the MS ecosystem for these kinds of applications.
Once Access could use SQL Server, it became worlds better. But the whole "GUI application interface" made it so expensive and limiting that it could never really be a great tool, even when it was a good enough tool.
I've got customers who have built way too much on it and even though they are tiny and use it about as well as anyone could, it's really clear that if they put a little effort into a PHP developer that they could replace everything in a week with something vastly better.
A week? you mean 40 hours at $250/hr (dev house)?
-
@Dashrender said in Access 2003 in a 2021 World???:
@scottalanmiller said in Access 2003 in a 2021 World???:
@Pete-S said in Access 2003 in a 2021 World???:
@Dashrender said in Access 2003 in a 2021 World???:
@DustinB3403 said in Access 2003 in a 2021 World???:
And yes I know that best is relative to ones needs.
Access was the "best" at one point I'm sure.
I'm willing to bet that's not true - not a lot.. maybe $100... lol pretty sure Access was never the best for anything.. other solutions while possibly more difficult could still likely be shown to be much better solutions.
It wasn't Access itself that was the thing. It was the JET database engine that Access used under the hood that made it popular.
Back in the 90's if you wanted a simple database in your application and you used something like Visual Basic 3.0 then the JET engine was the first option to consider because Microsoft bundled it with VB and it was free. That's how it gained a foothold.
The JET engine was very very far from the best or even good. It was common to corrupt the database and run tools to "repair" it. But it was available without any effort - today we know that is perhaps the most important "feature"...
If you wanted the best you'd connect your application to an Oracle db.
MS Access itself was never a serious tool that developers used for business applications. It's very limited so VB was the default choice in the MS ecosystem for these kinds of applications.
Once Access could use SQL Server, it became worlds better. But the whole "GUI application interface" made it so expensive and limiting that it could never really be a great tool, even when it was a good enough tool.
I've got customers who have built way too much on it and even though they are tiny and use it about as well as anyone could, it's really clear that if they put a little effort into a PHP developer that they could replace everything in a week with something vastly better.
A week? you mean 40 hours at $250/hr (dev house)?
40 hours, a PHP dev sure isn't $250/hr. That's an ERP cost per hour. Contract a developer for a week and you can definitely find someone who will work at much more like $85/hr if you shop around and find someone available.
