In the meantime, the "complete workaround" is to remove the Format
property's value from the field's properties in the table's design view.
Otherwise, concatenating the field's value with an empty string also seems
to "overcome" the problem.
--
Ken Snell
<MS ACCESS MVP>
"nms" <n...@discussions.microsoft.com> wrote in message
news:79710485-1C84-4047...@microsoft.com...
In the meantime, the "complete workaround" is to remove the Format
property's value from the field's properties in the table's design view.
Otherwise, concatenating the field's value with an empty string also seems
to "overcome" the problem.
--
Ken Snell
<MS ACCESS MVP>
"nms" <n...@discussions.microsoft.com> wrote in message
news:79710485-1C84-4047...@microsoft.com...
--
Ken Snell
<MS ACCESS MVP>
"nms" <n...@discussions.microsoft.com> wrote in message
news:B0E7E50F-21B0-4A28...@microsoft.com...
This is why, IMHO, you should *never* update to a new service pack until
things have been shaken out a bit!
--
There's ALWAYS more than one way to skin a cat!
Answers/posts based on Access 2000
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-forms/200709/1
MS has not released information about when the fix will be published.
--
Ken Snell
<MS ACCESS MVP>
"st8employee" <st8em...@discussions.microsoft.com> wrote in message
news:BDAE5B3F-6E71-41F0...@microsoft.com...
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Graham" <Gra...@discussions.microsoft.com> wrote in message
news:6E87895E-3802-43A6...@microsoft.com...