Version number will vary with the organization and application. A good developer should be able to handle the current version and go back a couple of versions as well, knowing in general what changes from version to version.
Validating that existing SW and apps built on a current version will continue to work with a new version is a considerable effort, but necessary. I work in IT for a hospital, so problems need to be anticipated and eliminated, not fixed on the fly.
We also have 1 vendor product based on Access 2003 and cannot advance versions without breaking the system, Access 2010 is the latest version that will work with those files.
Word/Excel/PowerPoint are a lot more flexible with different versions than is Access.
Gary
At 05:17 PM 3/4/2018, you wrote:
I notice the books listed in Ray's note are for Access 2010 or older. I, too, would like to improve my skills with Access. Given that I have Access 2016, are those older books the way to go? Or should I look for books for Access 2016? I'd like to make the best use of what will likely be a substantial amount of time.
Steve
Posted by: "Gary D. Schwartz" <gary.schwartz@pobox.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
Tidak ada komentar:
Posting Komentar