Jumped into Access and DB management with both feet, without checking the water.
I inherited a database that began as handwritten unpublished accounts from the 1800's, to state published data, eventually to dBase, then migrated to Access. I work for a state agency and nearly all of our data, published or not (including the database itself), is public access: What data we can provide is available in physical form and/or via web at no end user cost. A great mission, a great team, and a fantastic work environment.
Our data is georeferenced, and some prior experience in managing ArcGIS data has migrated well to Access. I have experience programming in Python, and a tad in VB. I enjoy writing little scripts that make my, and my co-workers, life a bit easier or more efficient.
I'm joining this forum because I am in a long-term relationship with a large and developing database that I didn't create. Part of my job is to fix what is wrong now, some issues that have been inherited from, literally, the 1800's (how awesome is that!?! I love pulling my hair out!) and dealing with the band-aids that have been used to get it up on the web and keep it running as new data was collected. We are also getting prepared for a substantial change to the functionality of our public interface, and the way data will be collected and organized in our db. The creators are retired, and as a non-profit agency on a stretched budget I wear several hats. And database management happens to be one of mine. Things are generally going well, but I need somewhere to turn when I get stymied. I'm looking forward to hearing from the experts
I inherited a database that began as handwritten unpublished accounts from the 1800's, to state published data, eventually to dBase, then migrated to Access. I work for a state agency and nearly all of our data, published or not (including the database itself), is public access: What data we can provide is available in physical form and/or via web at no end user cost. A great mission, a great team, and a fantastic work environment.
Our data is georeferenced, and some prior experience in managing ArcGIS data has migrated well to Access. I have experience programming in Python, and a tad in VB. I enjoy writing little scripts that make my, and my co-workers, life a bit easier or more efficient.
I'm joining this forum because I am in a long-term relationship with a large and developing database that I didn't create. Part of my job is to fix what is wrong now, some issues that have been inherited from, literally, the 1800's (how awesome is that!?! I love pulling my hair out!) and dealing with the band-aids that have been used to get it up on the web and keep it running as new data was collected. We are also getting prepared for a substantial change to the functionality of our public interface, and the way data will be collected and organized in our db. The creators are retired, and as a non-profit agency on a stretched budget I wear several hats. And database management happens to be one of mine. Things are generally going well, but I need somewhere to turn when I get stymied. I'm looking forward to hearing from the experts
