Hi Norbert,
I'd start with "We have a problem and it's Access 2013." This immediately puts you and your client on the same side of the table with Access 2013 on the other side as the problem that you need to, together, solve. Make certain that you have the correct people, or decision makers, in your partnership.
Then after establishing a partnership against Access 2013, I'd stress the personal benefits and return on investment your client will accrue if Access 2010 is used in place of 2013. These benefits ought to be visible from the start simply because they'll not be having to have to "fix" stuff all the time to overcome the 2013 bugs and users won't be waiting for the tool they need to do their job.
I'd then make sure that the initial "target" of the change from Access 2013 to 2010 is the client management of those who will continue to use the database. This is to ensure that "sponsorship" is in place and that the person or person's responsible for "signing their paychecks" are behind the need to change and want it to happen. It's the sponsor or sponsors who need to communicate the "what, why, and how" the change is happening, not once, but on an ongoing basis. Part of this communication needs to be to describe the "desired state" for what things will look like after the change to Access 2010 so that everyone has a vision of the way things will be after the change.
Finally, I'd stress the anchors, or things that are not changing, so that as the change to introduce 2010 across their organization is implemented, they will still have things with which thay are familiar so that everything isn't new.
All this wonderfulness is part of the effort to introduce change across an organization. In this case, the change is minor in that it's simply replacing Access 2013 with 2010 and probably won't need a lot of effort once the first 2 things above are accomplished. Keep it simple but definitely get the decision makers on your side with Access 2013 as tghe problem that can be solved by going to 2010.
Maybe this will help.
Jeff
I'd start with "We have a problem and it's Access 2013." This immediately puts you and your client on the same side of the table with Access 2013 on the other side as the problem that you need to, together, solve. Make certain that you have the correct people, or decision makers, in your partnership.
Then after establishing a partnership against Access 2013, I'd stress the personal benefits and return on investment your client will accrue if Access 2010 is used in place of 2013. These benefits ought to be visible from the start simply because they'll not be having to have to "fix" stuff all the time to overcome the 2013 bugs and users won't be waiting for the tool they need to do their job.
I'd then make sure that the initial "target" of the change from Access 2013 to 2010 is the client management of those who will continue to use the database. This is to ensure that "sponsorship" is in place and that the person or person's responsible for "signing their paychecks" are behind the need to change and want it to happen. It's the sponsor or sponsors who need to communicate the "what, why, and how" the change is happening, not once, but on an ongoing basis. Part of this communication needs to be to describe the "desired state" for what things will look like after the change to Access 2010 so that everyone has a vision of the way things will be after the change.
Finally, I'd stress the anchors, or things that are not changing, so that as the change to introduce 2010 across their organization is implemented, they will still have things with which thay are familiar so that everything isn't new.
All this wonderfulness is part of the effort to introduce change across an organization. In this case, the change is minor in that it's simply replacing Access 2013 with 2010 and probably won't need a lot of effort once the first 2 things above are accomplished. Keep it simple but definitely get the decision makers on your side with Access 2013 as tghe problem that can be solved by going to 2010.
Maybe this will help.
Jeff
From: "drnorbert@msn.com [MS_Access_Professionals]" <MS_Access_Professionals@yahoogroups.com>
To: "MS Access Professionals" <MS_Access_Professionals@yahoogroups.com>
Sent: Sunday, January 11, 2015 11:37:57 AM
Subject: [MS_AccessPros] MSAccess 2013 very buggy
--
To: "MS Access Professionals" <MS_Access_Professionals@yahoogroups.com>
Sent: Sunday, January 11, 2015 11:37:57 AM
Subject: [MS_AccessPros] MSAccess 2013 very buggy
Hi all Happy New Year!
I have been using Access 2013 for about 2 years with a large application (250K lines of code, 300 forms, 250 reports, 25 modules, backend SQL 2012) and after many experiences of different bugs including freezing screens, unstable filters, code freezes without any logic reason, etc I came to the conclusion that John Viescas is 110% correct when he is telling us that 2013 is very buggy .
I changed now to 2010 and none of the issues I had with 2013 are present.
The conflict I have now is how I can explain to my client that they have to switch to 2010.
Please share any comments you have regarding my statement and conflicts.
Thanks
Norbert
--
---
Jeffrey Park Jones
Excel, Access, Word, Office Expert
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
jpjones23@centurylink.net
Jeffrey Park Jones
Excel, Access, Word, Office Expert
919-671-9870
5109 Deer Lake Trail
Wake Forest, NC 27587
jpjones23@centurylink.net
__._,_.___
Posted by: jpjones23@centurylink.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (2) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar