Hi

After upsizing..

In the access 97 front end forms, if i try to add data to a memo field i get
an ODBC error.

in SQL 2000, i've tried changing the data type of the field from ntext to
text but i still get an error.

the error is something like:

Factional Truncation #0 cannot (?????) to text, ntext or image data types
unless using IS NULL or LIKE oporator....#306

(sorry, don't have full message infront of me).

does anyone have any idea what the problem might be??

thanks

Jado

Hi
in case of access 97 - all fields have to be non-unicode (text, varchar) in
SQL server, then access will proper handle them
also make sure you have a timestamp field in your table

BTW - there is an utility to convert to and from unicode types:
http://www.pointltd.com/Downloads/Details.asp?dlID=42

--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com



"Jado" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
>
> After upsizing..
>
> In the access 97 front end forms, if i try to add data to a memo field i
> get
> an ODBC error.
>
> in SQL 2000, i've tried changing the data type of the field from ntext to
> text but i still get an error.
>
> the error is something like:
>
> Factional Truncation #0 cannot (?????) to text, ntext or image data types
> unless using IS NULL or LIKE oporator....#306
>
> (sorry, don't have full message infront of me).
>
> does anyone have any idea what the problem might be??
>
> thanks
>
> Jado
>
>

Thanks Alex..

I'll try the suggested, and got back if any issues.

Jado

"Alex Dybenko" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
> in case of access 97 - all fields have to be non-unicode (text, varchar)
in
> SQL server, then access will proper handle them
> also make sure you have a timestamp field in your table
>
> BTW - there is an utility to convert to and from unicode types:
> http://www.pointltd.com/Downloads/Details.asp?dlID=42
>
> --
> Alex Dybenko (MVP)
> http://Alex.Dybenko.com
> http://www.PointLtd.com
>
>
>
> "Jado" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi
> >
> > After upsizing..
> >
> > In the access 97 front end forms, if i try to add data to a memo field i
> > get
> > an ODBC error.
> >
> > in SQL 2000, i've tried changing the data type of the field from ntext
to
> > text but i still get an error.
> >
> > the error is something like:
> >
> > Factional Truncation #0 cannot (?????) to text, ntext or image data
types
> > unless using IS NULL or LIKE oporator....#306
> >
> > (sorry, don't have full message infront of me).
> >
> > does anyone have any idea what the problem might be??
> >
> > thanks
> >
> > Jado
> >
> >
>
>

Hi Alex

i've tried the sugessted and it works. Thanks.

why do i need the TimeStamp field and should i be doing anything with it?

currently it's just sitting there!

also, i've tried this on a fresh new db...will it work on db's that already
contain data?

thanks

Jado
"Alex Dybenko" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi
> in case of access 97 - all fields have to be non-unicode (text, varchar)
in
> SQL server, then access will proper handle them
> also make sure you have a timestamp field in your table
>
> BTW - there is an utility to convert to and from unicode types:
> http://www.pointltd.com/Downloads/Details.asp?dlID=42
>
> --
> Alex Dybenko (MVP)
> http://Alex.Dybenko.com
> http://www.PointLtd.com
>
>
>
> "Jado" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Hi
> >
> > After upsizing..
> >
> > In the access 97 front end forms, if i try to add data to a memo field i
> > get
> > an ODBC error.
> >
> > in SQL 2000, i've tried changing the data type of the field from ntext
to
> > text but i still get an error.
> >
> > the error is something like:
> >
> > Factional Truncation #0 cannot (?????) to text, ntext or image data
types
> > unless using IS NULL or LIKE oporator....#306
> >
> > (sorry, don't have full message infront of me).
> >
> > does anyone have any idea what the problem might be??
> >
> > thanks
> >
> > Jado
> >
> >
>
>

Hi Jado,
if you use text fields in sql server table, linked to access, then adding a
timestamp field helps jet to update table, actually it use it to locate row

--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com


"Jado" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Alex
>
> i've tried the sugessted and it works. Thanks.
>
> why do i need the TimeStamp field and should i be doing anything with it?
>
> currently it's just sitting there!
>
> also, i've tried this on a fresh new db...will it work on db's that
> already
> contain data?
>
> thanks
>
> Jado
> "Alex Dybenko" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Hi
>> in case of access 97 - all fields have to be non-unicode (text, varchar)
> in
>> SQL server, then access will proper handle them
>> also make sure you have a timestamp field in your table
>>
>> BTW - there is an utility to convert to and from unicode types:
>> http://www.pointltd.com/Downloads/Details.asp?dlID=42
>>
>> --
>> Alex Dybenko (MVP)
>> http://Alex.Dybenko.com
>> http://www.PointLtd.com
>>
>>
>>
>> "Jado" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > Hi
>> >
>> > After upsizing..
>> >
>> > In the access 97 front end forms, if i try to add data to a memo field
>> > i
>> > get
>> > an ODBC error.
>> >
>> > in SQL 2000, i've tried changing the data type of the field from ntext
> to
>> > text but i still get an error.
>> >
>> > the error is something like:
>> >
>> > Factional Truncation #0 cannot (?????) to text, ntext or image data
> types
>> > unless using IS NULL or LIKE oporator....#306
>> >
>> > (sorry, don't have full message infront of me).
>> >
>> > does anyone have any idea what the problem might be??
>> >
>> > thanks
>> >
>> > Jado
>> >
>> >
>>
>>
>
>