Ahhhh ... its such a relief when the problem is something as a simple as a
typo. Hopefully it didn't put a deadline in jeopardy.
A lot of my Director work is database related with clients supplying data.
Over the years I've become conditioned to checking key field entries for
typos. Most notably ...
-- extra spaces before and after an entry
-- extra return characters
-- the letter "O" versus the number "0". Its obvious if the right font is
used but that one caused me a lot of grief about 5 years ago. A hard drive
full of images that were sorted by uppercase 3 character codes. I always use
Monaco in the Finder now.
-- "l" versus "1" as you've noted
-- and of course basic spelling mistakes which may not be as easy to catch
Anyone else have a favourite database typo?
Cheers,
Randy
on 3/1/01 12:13 AM, Kerry Thompson at [EMAIL PROTECTED] wrote:
> After many alert boxes and a lot of head scratching, I used charToNum() to
> get the ASCII values for the parameter name. You guessed it--the second
> declaration, within the <embed> tag, was swl (that's the letter l, not the
> numeral 1).
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
