Long Records Giving me Grief!
  Home FAQ Contact Sign in
microsoft.public.data.ado only
 
Advanced search
POPULAR GROUPS

more...

microsoft.public.data.ado Profile…
 Up
Long Records Giving me Grief!         


Author: Siegfried Heintze
Date: Jun 13, 2008 15:46

I fixed (kinda) my problem by truncating my records to 250 chars.

I'm automating the creation of my database and table definition using VB
Script.

When I use the UI I see there is another datatype called memo. However, when
I look at http://msdn.microsoft.com/en-us/library/ms675318(VS.85).aspx I
don't see such a datatype.

Will using type memo alleviate the 255 character constraint? How big can
memos be?

What is the number value for the constant adMemo
-- I did not see it at
http://msdn.microsoft.com/en-us/library/ms675318(VS.85).aspx.

Thanks,
Siegfried
1 Comment
Re: Long Records Giving me Grief!         


Author: Bob Barrows [MVP]
Date: Jun 14, 2008 06:25

Siegfried Heintze wrote:
> I fixed (kinda) my problem by truncating my records to 250 chars.
>
> I'm automating the creation of my database and table definition using
> VB Script.
>
> When I use the UI I see there is another datatype called memo.

So this must be an Access (Jet) database? Are both the source and
destination databases Access?
> However, when I look at
> http://msdn.microsoft.com/en-us/library/ms675318(VS.85).aspx I don't
> see such a datatype.
>

Right. It's an access-specific name. The corresponding JetSQL name is,
confusingly, "TEXT". The JetSQL name for the Access "Text" datatype is
"CHARACTER" ("CHAR" can also be used).
> Will using type memo alleviate the 255 character constraint? How big
> can memos be?
Show full article (1.60Kb)
no comments