Need MS Access app re-written to something else.
-
Why not use Access?
-
@carnival-boy said in Need MS Access app re-written to something else.:
Why not use Access?
Lack of portability is the main reason. You might get lucky and find that the setup is simple enough to move from version to version, but then again, might not.
Also, why force yourself to have a $400+ Access license? Or a $20 OEM Windows license or a $100+ FBP Windows license, etc.
-
Not sure they're generally valid reasons. All systems require time and effort for upgrades, new versions etc etc.
Most companies already have Access licences as part of their Microsoft 365 account.
However, I see that Access doesn't run on a Mac which sounds like a showstopper.
-
@carnival-boy said in Need MS Access app re-written to something else.:
Most companies already have Access licences as part of their Microsoft 365 account.
Well, most companies don't have O365 at all. Many do, but not most.
And lots, maybe not most, don't get it with Access. But definitely lots.
Having access to Access isn't uncommon, but it is not the norm.
-
@carnival-boy said in Need MS Access app re-written to something else.:
Why not use Access?
Cost to acquire (assumed.) Cost to support (higher than something more robust.) Performance. Portability. Security. Reliability. And no need to lock in to SQL Server.
Access doesn't run on a phone, on a Raspberry Pi, on a Mac, on a Chromebook. Even in orgs that don't have any of those today, choosing Access means making a commitment to not having them without replacing that system... again.
If Access was cheaper or easier... there'd be a good argument for it. But I doubt that it is. PHP isn't hard and making an Access-parity app in it is often about the same time as making it in Access. But with so many benefits.
-
@dashrender said in Need MS Access app re-written to something else.:
@carnival-boy said in Need MS Access app re-written to something else.:
Why not use Access?
Lack of portability is the main reason. You might get lucky and find that the setup is simple enough to move from version to version, but then again, might not.
Also, why force yourself to have a $400+ Access license? Or a $20 OEM Windows license or a $100+ FBP Windows license, etc.
And don't forget that to have it be in any sense serious at all (not that any use of a client-server system is serious, but that's as good as Access gets) means maintaining a Windows Server license for the database and MS SQL Server. SQL Server might be free, but only at really small uses. If this grows or is large in any way, you might end up having to pay for and maintain SQL Server licensing, too.
The potentially for there to be lots of costs and lock-ins to those costs are high. Not guaranteed, but high.
-
I didn't get the impression from the OP that they were use SQL Server - less than 500 lines of code.
-
@carnival-boy said in Need MS Access app re-written to something else.:
I didn't get the impression from the OP that they were use SQL Server - less than 500 lines of code.
He point was - if you want to be "serious" about this project, and not be just someone's pet project.
While I think Scott's a bit overblown with the whole Windows Server and SQL server to be "serious" I see where he's coming from.
For example sticking with Windows 10 for example is likely fine because I'm assuming it's being run on and from a single machine connected to the gate system, not a remote server, etc... -
@carnival-boy said in Need MS Access app re-written to something else.:
I didn't get the impression from the OP that they were use SQL Server - less than 500 lines of code.
That's purely a configuration in Access. But the issue is, Access only works reliably with a small number of users until you switch it to SQL Server. Its design is that SQL Server is required for production use as intended for multi-user. Both for reliability, and security.
-
@dashrender said in Need MS Access app re-written to something else.:
While I think Scott's a bit overblown with the whole Windows Server and SQL server to be "serious" I see where he's coming from.
For example sticking with Windows 10 for example is likely fine because I'm assuming it's being run on and from a single machine connected to the gate system, not a remote server, etc...It's a licensing requirement if you want security and reliable multi-user access. Otherwise you have to use the shared-file system of a JetDB that is completely exposed to things like ransomware. And that is highly flaky once you have more than about five users.
-
@scottalanmiller said in Need MS Access app re-written to something else.:
@dashrender said in Need MS Access app re-written to something else.:
While I think Scott's a bit overblown with the whole Windows Server and SQL server to be "serious" I see where he's coming from.
For example sticking with Windows 10 for example is likely fine because I'm assuming it's being run on and from a single machine connected to the gate system, not a remote server, etc...It's a licensing requirement if you want security and reliable multi-user access. Otherwise you have to use the shared-file system of a JetDB that is completely exposed to things like ransomware. And that is highly flaky once you have more than about five users.
This really seems like a single computer setup - so while what you mention could be good, might be overkill for this setup.
-
@dashrender said in Need MS Access app re-written to something else.:
@scottalanmiller said in Need MS Access app re-written to something else.:
@dashrender said in Need MS Access app re-written to something else.:
While I think Scott's a bit overblown with the whole Windows Server and SQL server to be "serious" I see where he's coming from.
For example sticking with Windows 10 for example is likely fine because I'm assuming it's being run on and from a single machine connected to the gate system, not a remote server, etc...It's a licensing requirement if you want security and reliable multi-user access. Otherwise you have to use the shared-file system of a JetDB that is completely exposed to things like ransomware. And that is highly flaky once you have more than about five users.
This really seems like a single computer setup - so while what you mention could be good, might be overkill for this setup.
It is a Raspberry Pi setup, IMO. I think @JasGot is right on that.
I think he is off on the "wishing he had 5 hours" thing though.
I don't know enough about controlling Pi pins to handle this. I think that would be better than the serial interface for the relay control. But it will also require then new wiring which is physical.
The barcode readers should be a standard listen for input handler.
The database design should be pretty straightforward.
The user interface does not sound like it needs to be complex, but like anything, you need to make it comfortably usable, or users will not use.
Finally, security of the application, it's users, data, etc will have to be designed.
