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, July 2007, based on a posting by Peter Miller.
This article describes a bug in Access 2000 and later (JET 4 and later), where a memo field is displays incorrect characters under these conditions:
The display is typically one or two strange characters, instead of the contents of the memo field.
You can download the demonstration database shown below (10kb, zipped, Access 2000 format mdb.)
TableOne consists of two fields:
TableTwo has one Number field (Long Integer), with 3 records (the numbers 1, 2, and 3.) There are no indexes in either table.
The query joins the two tables, and groups by the fields in TableOne. The inset shows how JET displays the output of FieldB incorrectly.
Either of the following will work around the bug:
There is a similar bug where concatenated text fields yield garbage, but applies to recordsets only.
See truncation of memo fields for details of of how to avoid chopping off the contents at 255 characters.
|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 'Grouping by Memo field yields garbage'?
No comments yet.
Why not be the first to comment on this article?!
Have your say...