IN THE SPOTLIGHT: MDE to MDB Conversion Service
(also supports: ACCDE to ACCDB, ADE to ADP, etc)
IN THE SPOTLIGHT: vbWatchdog
VBA error handling just got easier...
" vbWatchdog is off the chart. It solves a long standing problem of how to consolidate error handling into one global location and avoid repetitious code within applications. "
- Joe Anderson,
Microsoft Access MVP
Meet Shady, the vbWatchdog mascot watching over your VBA code →
(courtesy of Crystal Long, Microsoft Access MVP)
IN THE SPOTLIGHT: vbMAPI
An Outlook / MAPI code library for VBA, .NET and C# projects
Get emails out to your customers reliably, and without hassle, every single time.
Use vbMAPI alongside Microsoft Outlook to add professional emailing capabilities to your projects.
Provided by Allen Browne, January 2004. Updated May 2006.
This feature was introduced in Access 2000. It tries to help users who rename a table field, so that queries, forms and reports automatically recognise the new field name. Microsoft has addressed some of the problems with this feature, but is it still buggy, incomplete, and a performance problem.
The workaround is to turn the feature off . In Access 2000 - 2003, checking the Name AutoCorrect boxes under Tools | Options | General. In Access 2007, click the Office Button | Access Options | Current Database, and scroll down to Name AutoCorrect Options. You must remember to do this every time you create a database, preferably before creating any other objects.
(Note: this is not the same as AutoCorrect for spelling, which has none of these problems.)
A scan of the knowledgebase reveals why we urge you to turn this feature off immediately.
It causes problems with queries:
It causes problems with forms:
It causes problems with reports:
It does not work at all with macros and code.
It fails with converted databases, imported objects, and messes up design-time licences:
It is a serious performance problem:
It causes Access to crash, therefore corrupting databases:
Turning off Name AutoCorrect means that the Access 2003 promise of tracing dependencies is unfulfilled, but that doesn't always work either according to this article: Incorrect Object Dependencies Information Appears for Database Objects in a Read-Only Database.
If you have existing databases where this feature is on, consider creating a new (blank) database, turning it off, and then importing all objects from your existing one (File | Get External | Import).
|Home||Index of tips||Top|
This is a cached tutorial, reproduced with permission.
Have your say - comment on this article.
What did you think of 'Failures caused by Name Auto-Correct (bugs)'?
No comments yet.
Why not be the first to comment on this article?!
Have your say...