Orthodox Dave
Home Developer
- Local time
- Today, 14:19
- Joined
- Apr 13, 2017
- Messages
- 218
Been programming in Access since 1995 - completely self-taught. Thank goodness for Google, and the "for dummies" books! In the 6 years before that it was DataEase :banghead:
During this time I designed and operated a Document Management database in the Oil and Gas Engineering industry, as a Senior Document Controller. So my job was the Document Control work and I had to fit in designing the database around that. I expect many will recognise that!
In September 2016 I was made redundant after 25 years with the company, so I decided to spend my time at home completely re-designing the database from the bottom up, so it would be my copyright and with the hope of selling it in the future, or at least learning more about Access. This is proving a real challenge, not least in finding ways to motivate myself!
My philosophy in database work is
1. If it can be automated it should be automated,
2. The database should allow for exceptions to the "norm",
3. The hardest work should be done by the programmer. If the user finds it hard or frustrating to use, that's the programmer's fault.
4. I'm sure there will be a 4. but I haven't thought of it yet!
I have seen too many databases that violate the above 1-3. For example:
1. Databases that could do so much more with the data they contain;
2. Databases where the input requirements are so rigid that the user can't input what really happened so has to alter this to fit the database criteria;
3. The user is expected to re-input stuff that's already in the database;
I've been visiting the Access-Programmers site from time to time, and today decided to join formally, mainly so I could contribute to discussions where possible.
I find Access programming proves frustrating almost daily! Every time I think I've got it sussed, the next bit of code sends me back to the drawing board!
But satisfying too! 
During this time I designed and operated a Document Management database in the Oil and Gas Engineering industry, as a Senior Document Controller. So my job was the Document Control work and I had to fit in designing the database around that. I expect many will recognise that!
In September 2016 I was made redundant after 25 years with the company, so I decided to spend my time at home completely re-designing the database from the bottom up, so it would be my copyright and with the hope of selling it in the future, or at least learning more about Access. This is proving a real challenge, not least in finding ways to motivate myself!
My philosophy in database work is
1. If it can be automated it should be automated,
2. The database should allow for exceptions to the "norm",
3. The hardest work should be done by the programmer. If the user finds it hard or frustrating to use, that's the programmer's fault.
4. I'm sure there will be a 4. but I haven't thought of it yet!
I have seen too many databases that violate the above 1-3. For example:
1. Databases that could do so much more with the data they contain;
2. Databases where the input requirements are so rigid that the user can't input what really happened so has to alter this to fit the database criteria;
3. The user is expected to re-input stuff that's already in the database;
I've been visiting the Access-Programmers site from time to time, and today decided to join formally, mainly so I could contribute to discussions where possible.
I find Access programming proves frustrating almost daily! Every time I think I've got it sussed, the next bit of code sends me back to the drawing board!
But satisfying too! 
