O, Experts! Please help me!
I have a new spreadsheet/Access database combo reporting system.
I need to store the Access file where other people can read it, probably from Excel spreadsheets, where I can prepare a few macros to refresh the data.
Issues
- Most end users are still using Excel 2003. The Access file and spreadsheets I build for them will be in 2007.
- I am not a programmer, only a dabbler in macros in Access and Excel.
- I plan to store the “master” database and spreadsheets on my C:\ drive, do updates there and then copy up to a shared drive daily. We all have permission to the Public share, and largely mapped to a P:\ drive, but I can’t guarantee it.
- Also not having been a developer, I am wondering how to best do versioning – I currently take the previous day, create a file.accdb.bak##, where ## is incremented and stored in a subfolder. Is there a better way?
- I have also a Development and a Production version of the database, and want to move new objects to Prod once they are ok’d – how to do naming conventions? Ensure they are pointing to the correct space? Is splitting the tables/queries the way to go and if so, how is that managed?
- I have (sadly) fallen into the common developer habit of all “doing” and never getting around to writing about what I did… How do I fix this?
I have looked for info, but any books I find are only about the programming itself – not the best practices of code control and documentation.
Any thoughts would be much appreciated!
Susan
I have a new spreadsheet/Access database combo reporting system.
I need to store the Access file where other people can read it, probably from Excel spreadsheets, where I can prepare a few macros to refresh the data.
Issues
- Most end users are still using Excel 2003. The Access file and spreadsheets I build for them will be in 2007.
- I am not a programmer, only a dabbler in macros in Access and Excel.
- I plan to store the “master” database and spreadsheets on my C:\ drive, do updates there and then copy up to a shared drive daily. We all have permission to the Public share, and largely mapped to a P:\ drive, but I can’t guarantee it.
- Also not having been a developer, I am wondering how to best do versioning – I currently take the previous day, create a file.accdb.bak##, where ## is incremented and stored in a subfolder. Is there a better way?
- I have also a Development and a Production version of the database, and want to move new objects to Prod once they are ok’d – how to do naming conventions? Ensure they are pointing to the correct space? Is splitting the tables/queries the way to go and if so, how is that managed?
- I have (sadly) fallen into the common developer habit of all “doing” and never getting around to writing about what I did… How do I fix this?
I have looked for info, but any books I find are only about the programming itself – not the best practices of code control and documentation.
Any thoughts would be much appreciated!
Susan
