Microsoft is making Access 2010 web hosting more mainstream:
http://blogs.msdn.com/b/access/archive/2010/10/19/office-365-and-access-web-databases.aspx
While another Access 2010 hosting solution exists already, clearly people look to Microsoft first to find the end-to-end solution. Whether the pricing will be comparable, that's going to be interesting.
Tuesday, October 19, 2010
Monday, September 27, 2010
Transitioning your Database
Some time ago I posted about the risk you face in creating a database that becomes essential for your group's daily operations. By no means should you think of NOT creating or pursuing the database. It is a double-edged sword: creating an innovative and useful database will increase your value and the success of your group, while it can also add to your workload and cause your management a bit of fear when they think of promoting you or your departure.
Step 1: Set Expectations
Set clear expectations with your management about what your Access database can do functionally, and what it can do with and without you. It may continue to work perfectly even if you are gone for weeks. Or it might need daily care and feeding. Either way, make sure you've communicated what it takes for your database to keep working, and what skill level is needed if you are gone. Ideally your manager will be an ally, and make certain to facilitate finding a prospective replacement. It also helps them to understand how much hard work you've put in to saving your group time and money.
Step 2: Find a Replacement
Look for someone in your group to begin sharing the work with. If your application has been visible to others in your group, you may have no trouble finding someone willing to start taking some of the "hero" spotlight. And you don't need to tell them you're hoping for a promotion, just that you'd like someone to help cover questions and issues if you're out of town, on vacation, or sick.
It's likely that no-one will have your level of expertise in Access. If so, you can try to convince your manager to fund an online Access class, or a book or two to help cross-train your colleague.
Step 3: The Transition
I've been fortunate to move to new positions several times in my career. At least three included a departmental Access database that needed someone to take care of when I moved on. Try setting up a series of short meetings to transition your responsibility. Breaking your transition into several sessions gives some breathing time for you to remember details you might want to pass on, and the new person can assemble questions and absorb the information for the next session. You may be tempted to apologize for poor code quality, imperfect architecture, and ineffecient steps. Rest assured the person you are transitioning to will likely not recognize these facts, and will have an opportunity to improve upon them in due course (if they have the interest!).
Step 1: Set Expectations
Set clear expectations with your management about what your Access database can do functionally, and what it can do with and without you. It may continue to work perfectly even if you are gone for weeks. Or it might need daily care and feeding. Either way, make sure you've communicated what it takes for your database to keep working, and what skill level is needed if you are gone. Ideally your manager will be an ally, and make certain to facilitate finding a prospective replacement. It also helps them to understand how much hard work you've put in to saving your group time and money.
Step 2: Find a Replacement
Look for someone in your group to begin sharing the work with. If your application has been visible to others in your group, you may have no trouble finding someone willing to start taking some of the "hero" spotlight. And you don't need to tell them you're hoping for a promotion, just that you'd like someone to help cover questions and issues if you're out of town, on vacation, or sick.
It's likely that no-one will have your level of expertise in Access. If so, you can try to convince your manager to fund an online Access class, or a book or two to help cross-train your colleague.
Step 3: The Transition
I've been fortunate to move to new positions several times in my career. At least three included a departmental Access database that needed someone to take care of when I moved on. Try setting up a series of short meetings to transition your responsibility. Breaking your transition into several sessions gives some breathing time for you to remember details you might want to pass on, and the new person can assemble questions and absorb the information for the next session. You may be tempted to apologize for poor code quality, imperfect architecture, and ineffecient steps. Rest assured the person you are transitioning to will likely not recognize these facts, and will have an opportunity to improve upon them in due course (if they have the interest!).
Thursday, August 19, 2010
Possible Game Changer from Microsoft
Creating an interface where normal business users can build an application without learning to program is the golden goose. Microsoft seemed to think Access was that product many years ago, here's their next evolution of it (I think). Beta is available August 23rd. Can't wait to take a test drive!
Thursday, August 12, 2010
Uploading Access to SQL Azure
Microsoft has just released an update to the SQL Server Migration Assistant (SSMA) that allows you to load your Access database into the Azure cloud. Haven't tried it yet, but please post a reply if you have. Would love to see what your experience has been. And specifically, how have you front-ended the database? With ASP.NET, or just continue to use the Access client with linked tables.
http://blogs.msdn.com/b/access/archive/2010/08/12/easily-migrate-access-data-to-sql-azure.aspx
http://blogs.msdn.com/b/access/archive/2010/08/12/easily-migrate-access-data-to-sql-azure.aspx
Wednesday, June 23, 2010
Office 2010 - Time to Upgrade
We've got quite a few Access customers still on 2003. Yesterday one asked if they should upgrade to 2007. The answer, of course, was "no." Naturally the conversation was directed to whether to upgrade to 2010 instead. You can find highlights for Access 2010 here. In the end, it's probably time for most users to upgrade to Office 2010 if you have 2003. The fact is 2003 was a legacy of Windows 95-era desktop apps, while 20007 and 2010 are more representative of Windows Vista/7 user experience design patterns and security. Not only will you find it easier (after some adjustment of course) to work in Office 2010, but security is also a key element to consider.
Access 2003 introduced a minimal security prompt, whereas the Office 2007/2010 Trust Center treats security in Office with the consideration it deserves. Office 2010 includes file-level trust, something definitely missing in 2007.
Lastly, if you are considering upgrading to Office 2010, you can reconsider whether all users require the full version of Access, or whether you can save money with the free Access runtime edition.
Access 2003 introduced a minimal security prompt, whereas the Office 2007/2010 Trust Center treats security in Office with the consideration it deserves. Office 2010 includes file-level trust, something definitely missing in 2007.
Lastly, if you are considering upgrading to Office 2010, you can reconsider whether all users require the full version of Access, or whether you can save money with the free Access runtime edition.
Saturday, June 19, 2010
Weekly Status Reports Online
A new online service from OpenGate Software! The free public beta period has started, sign up today for up to 10 users in your organization. Collect weekly status reports from your employees online, and submit to your manager in minutes. No more need to worry about status report templates, formatting, and reminders! Simple Status takes care of it all for you. Give it a try for free!
Friday, June 4, 2010
Subscribe to:
Posts (Atom)