MePenguin2000
Technical User
Hi,
I'm currently maintaining a smallish MS Access database app (frontend-backend split, ca 1M records) which is sporadically used by about 50 people worldwide. It's mainly analytical in nature so the software features have taken priority over database design (i.e. db is not particularly good!). Data is added centrally to the backend and then updates distributed to users, as are frontend updates.
We're at a point where we would like to turn the whole thing into a multi-user database, net accessible, add GIS features and the ability to link with related databases (scientific). We haven't decided on either a web based interface, or a standalone frontend which can store data in the field to upload on connection... or both (users vs administrators).
I've been recommended PostgreSQL and PostGIS, as an alternative to the VStudio Express, MS SQLServer and (eg.)ArcGIS route initially intended. I've had a look at phpPgAdmin, created a simple db and played a bit with PostGIS. It all seems good, but is clearly a level above my somewhat amateurish attempts in Access. I'm a VBA coder and a scientist really; not a db expert.
So my questions are:
1) As a VBA/Access programmer is it going to be a seriously long haul to convert everything to Postgre?
2) Would I be better off sticking with Visual Studio and SQL Server (this is an educational project, so MS is cheap even if not OpenSource)?
3) Would the combination of VStudio to develop the front end (VB, ODBC) and Postgre for the backend and GIS be sensible? Assuming I could get people to help me with the heavy duty db bits.
4) Are there any other options/combinations that would be easier?
Bonus question:
If I was to start a completely new and much larger project: multiuser db, GIS, advanced interfaces, with a couple of developers to help what setup would you recommend?
Sorry for the ramble, and thanks in advance,
Phil
I'm currently maintaining a smallish MS Access database app (frontend-backend split, ca 1M records) which is sporadically used by about 50 people worldwide. It's mainly analytical in nature so the software features have taken priority over database design (i.e. db is not particularly good!). Data is added centrally to the backend and then updates distributed to users, as are frontend updates.
We're at a point where we would like to turn the whole thing into a multi-user database, net accessible, add GIS features and the ability to link with related databases (scientific). We haven't decided on either a web based interface, or a standalone frontend which can store data in the field to upload on connection... or both (users vs administrators).
I've been recommended PostgreSQL and PostGIS, as an alternative to the VStudio Express, MS SQLServer and (eg.)ArcGIS route initially intended. I've had a look at phpPgAdmin, created a simple db and played a bit with PostGIS. It all seems good, but is clearly a level above my somewhat amateurish attempts in Access. I'm a VBA coder and a scientist really; not a db expert.
So my questions are:
1) As a VBA/Access programmer is it going to be a seriously long haul to convert everything to Postgre?
2) Would I be better off sticking with Visual Studio and SQL Server (this is an educational project, so MS is cheap even if not OpenSource)?
3) Would the combination of VStudio to develop the front end (VB, ODBC) and Postgre for the backend and GIS be sensible? Assuming I could get people to help me with the heavy duty db bits.
4) Are there any other options/combinations that would be easier?
Bonus question:
If I was to start a completely new and much larger project: multiuser db, GIS, advanced interfaces, with a couple of developers to help what setup would you recommend?
Sorry for the ramble, and thanks in advance,
Phil