Access Application - Training a Backup Developer
Hello, experts -
I have a developed a fairly robust application consisting of an Access 2010 front end with a backend SQL Server DB. It has some Office automation features and other bells and whistles. It has become fairly important and entrenched in our operation, and as such I need to train a couple of backup developers in case I get hit by a bus or decide to retire someday.
My question isn't technical - instead I am interested if anyone has an outline or other ideas about the best way to approach this transfer of knowledge to a new developer so they can support the application.
Unfortunately, the two people I've been given as backups have varying levels of experience using VBA, so I believe I may also be doing some advanced VBA training along the way, as well as orienting them on the application.
Any ideas or experiences you would care to share would be most appreciated!
I have a developed a fairly robust application consisting of an Access 2010 front end with a backend SQL Server DB. It has some Office automation features and other bells and whistles. It has become fairly important and entrenched in our operation, and as such I need to train a couple of backup developers in case I get hit by a bus or decide to retire someday.
My question isn't technical - instead I am interested if anyone has an outline or other ideas about the best way to approach this transfer of knowledge to a new developer so they can support the application.
Unfortunately, the two people I've been given as backups have varying levels of experience using VBA, so I believe I may also be doing some advanced VBA training along the way, as well as orienting them on the application.
Any ideas or experiences you would care to share would be most appreciated!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for your words of wisdom, Jeff!
I guess you're right - I will have to start at the beginning and see how much they already know about Access in general and move into the code a bit later. Unfortunately in our org of >10,000 employees, good Access developers are either hard to find or are good at hiding (I'm guessing the latter). So I will take what I have been offered and train them up as best I can.
Your point about troubleshooting is a great one - basic troubleshooting skills are so important - and also training end users to take screenshots of any errors, and keep track of what they were doing at the time! I have saved all my emails with various errors we've experienced during the development process. I think that would be a good place to start.
As far as making changes, I actually have a very detailed process of how to move objects from DEV to TEST to PROD, so we'll practice that as well.
We've got a list of enhancement requests, so figure I'll work on together with them on the less urgent ones until they prove or develop the required level of skills to fly on their own. Probably start them on developing reports, etc. and let them graduate to functions that actually manipulate data.
Just thinking through the order of things helps - thanks!
I guess you're right - I will have to start at the beginning and see how much they already know about Access in general and move into the code a bit later. Unfortunately in our org of >10,000 employees, good Access developers are either hard to find or are good at hiding (I'm guessing the latter). So I will take what I have been offered and train them up as best I can.
Your point about troubleshooting is a great one - basic troubleshooting skills are so important - and also training end users to take screenshots of any errors, and keep track of what they were doing at the time! I have saved all my emails with various errors we've experienced during the development process. I think that would be a good place to start.
As far as making changes, I actually have a very detailed process of how to move objects from DEV to TEST to PROD, so we'll practice that as well.
We've got a list of enhancement requests, so figure I'll work on together with them on the less urgent ones until they prove or develop the required level of skills to fly on their own. Probably start them on developing reports, etc. and let them graduate to functions that actually manipulate data.
Just thinking through the order of things helps - thanks!
Yes, ...also keep in mind that Access development is something a person should be "interested in", ...not "forced to learn"
;-)
Some people are good a math, others Literature,
Some people just want to use the database, and go home,
...other will want to stay and learn more...
The Access/Excel users might be a good place to start looking for candidates.
Good Luck.
;-)
Jeff
;-)
Some people are good a math, others Literature,
Some people just want to use the database, and go home,
...other will want to stay and learn more...
The Access/Excel users might be a good place to start looking for candidates.
Good Luck.
;-)
Jeff
ASKER