Hi.
Being new here I'd like to introduce myself. I'm 69 years old and have been using Access since 1993. However, I haven't used it for the last decade so I am in the process of remembering a lot of what I have forgotten. Thank God for Google!
The reason why I have returned to Access is that I'm the webmaster of a U3A here in Australia and intend to place the tables into the our webpage (hidden and password protected of course) and using Python let my fellow committee members interrogate the db via query by forms.
To that end, I have created this db using PostgreSQL as the backend. I did this because I have had experience with Oracle and Postgres is the closest to Oracle that I have seen. I sometimes wonder if I made the right decision and should have used MySQL instead but here I am. I have noticed that Access, when experiencing troubles with the backend, usually because of changed table structure which I've forgotten to update in Access, crashes and burns. There seems little error checking with Access in this case as I'm sure the crashing and burning could be alleviated with some simple error catching from Microsoft.
The database itself catches members, financial postion, courses being used etc. It has about 10 data tables and the equal number of look up tables so is quite simple. I can email receipts from it to the members (assuming they have email of course), print out receipts and in general use it as a management tool.
It's fun getting back into Access even though the cursing and carry on from me has at times been epic.
Being new here I'd like to introduce myself. I'm 69 years old and have been using Access since 1993. However, I haven't used it for the last decade so I am in the process of remembering a lot of what I have forgotten. Thank God for Google!
The reason why I have returned to Access is that I'm the webmaster of a U3A here in Australia and intend to place the tables into the our webpage (hidden and password protected of course) and using Python let my fellow committee members interrogate the db via query by forms.
To that end, I have created this db using PostgreSQL as the backend. I did this because I have had experience with Oracle and Postgres is the closest to Oracle that I have seen. I sometimes wonder if I made the right decision and should have used MySQL instead but here I am. I have noticed that Access, when experiencing troubles with the backend, usually because of changed table structure which I've forgotten to update in Access, crashes and burns. There seems little error checking with Access in this case as I'm sure the crashing and burning could be alleviated with some simple error catching from Microsoft.
The database itself catches members, financial postion, courses being used etc. It has about 10 data tables and the equal number of look up tables so is quite simple. I can email receipts from it to the members (assuming they have email of course), print out receipts and in general use it as a management tool.
It's fun getting back into Access even though the cursing and carry on from me has at times been epic.
