What is a suitable replacement for an Access 2003 database required to run an older PC?
Many years ago, I wrote a small Access 2003 database for a non-profit to track the donations they received. They recently wrote me asking for some new features (I was shocked it was still in use, honestly) and I’m wondering if I could rewrite the application with a newer technology/framework. Here are the machine specs:
We are moving an Access based corporate front-end into a Web-based App [closed]
Closed 5 years ago.
Enterprise application with lots of SQL queries
Context:
Place measurement data in database (access)
In a software I use records of measurement data. Each record contains basic information like a name, some parameters and the actual measurement data in the form of three arrays of double values that may vary in length from record to record. I currently use a binary format to save these records.
However I am not entirely happy with this approach, since it makes it hard to maintain (there may be changes or additional information in new versions and so on).
Implementing a Username Class
I am attempting to encapsulate several features about a user in a single class. Although the main use for this class would be to initialize it once and never have to call set any variables again, I would like this class to be scalable to be called many times. Although by putting this into a class I feel like I am either over-complicating it or breaking OOP standards.