Re: Strange Overflow Error!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Griff (Howling_at_The.Moon)
Date: 01/04/05 

Date: Tue, 4 Jan 2005 12:36:46 -0000

Strange indeed...it sounds to me like you've covered all the obvious bases.

Exploring a bit further the NULL problems, one bit of defensive coding you
could try would be to concatenate it with an empty string on the left hand
side rather than the right (either "" or I think vbNullString may work)

Desc = Replace(Left("" & rsGoods!goodsDescription, 255), vbCrLf, " ") '

Two extremely minor things....
    If it's a string, Left$() is I believe slightly faster than Left()
    I read somewhere that vbNewLine was preferred to vbCrLf.

I'm not that familiar with TEXT fields; I presume that it's nothing to do
with double-width characters (e.g. Unicode NVARCHAR vs VARCHAR)?

Good luck

Griff

Relevant Pages

  • Re: I dont quite get this "string".find()
    ... to make a special case out of searching for an empty string. ... Ahh, it's still darned strange:). ... my solution is not to search for empty strings <wink>. ...
    (comp.lang.python)
  • Re: coredump in df_readascii
    ... OS: AS3 ... Reason: df_commentschars is null. ... Strange. ... You can set it to an empty string, ...
    (comp.graphics.apps.gnuplot)
  • Re: editing docvariable fields
    ... Very strange indeed, especially as vbcr *is* chr. ... the ASC() function. ... As for the empty string, I checked it -- perhaps it's ...
    (microsoft.public.word.vba.userforms)
  • Re: I dont quite get this "string".find()
    ... But I guess an empty string isn't nothing, ... Ahh, it's still darned strange:). ... > def find(haystack, needle): ...
    (comp.lang.python)