Yes, good suggestion - I also find that it is necessary to replace data fields in actions when transferring tafs from one database to another, and one Tango platform to another sometimes - possibly because there is a bug in the way that it stores the information for development Vs. deployment data sources.

But I figured out the problem. Since I use a different database to test on my dev system than Access and the ODBC field selection is different from Access, I was using Varchar for the MEMO fields, but after changing them to LongChar it works fine.

thanks for the input.
Garth

I've never had any trouble with Memo fields in Access.
Why don't you try recreating the database actions from
scratch? That might take care of it.

Stefan

At 11:43 PM 9/11/2003 +1000, you wrote:
Anyone experienced problems with reading and writing to a MEMO field in an Access database?
It seems that if the characters are over 1024k it just won't update, and if the field is empty it won't read it. I get a precision error messages.


I'm using Witango 5 app (win 2k) server, but these are T2k files created on a Mac (if I remember rightly they were working Ok when they were T3 files (mac) running on the same server, so it may be something to do with how the T2k editor handles the ODBC.

cheers
--
Garth Penglase
Broadband Media
http://bbmedia.com.au
ph: 0500 527 000
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

======================================================== Database WebWorks: Dynamic web sites through database integration http://www.DatabaseWebWorks.com ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf


--
Garth Penglase
Broadband Media
http://bbmedia.com.au
ph: 0500 527 000
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to