Thanks Doug for the response.
I don't completely follow your suggestion.
are you saying something like the following.
dim myconn as new ado.connection, mytextfield() as string, myrs as new
myconn.open = "connection string to odbc database"
myrs.open("select memofield, nonmemofield from odbctable",myconn)
for i ....
The above code doesn't work, the myrs("memofield") is still null.
You did give me an idea of querying in dao and put the resulting recordset
in variables and playing with them. I would like to avoid all this code
(thats why I use vb and this ado stuff which is supposed to save me from
I also discovered that in using dao, if I query with an odbc direct
workspace I have no problems, but if I query with a jet workspace, than I
have the same problem as if I query with ado. I've been searching the
literature for an ado equivalent of an odbc workspace but can't find it.
Does it exist?
> I've had a simular problem with "text" fields coming from Foxpro tables in
> The only way I could get around it was to DIM a variable to store the
> field in. When your recordset is open, set the 'text' fields to variable
> BEFORE any other fields are accessed in your recordset. I am speaking
> code recordsets and not bound. If you are binding then I'm not sure how
> get around this but maybe this can point you in the right direction
> Doug Durrett
> Microsoft Certified Professional
> Analytix, Inc.
> 9461 Dielman Rock Island
> St. Louis, MO 63132
> (888) 991-8649
> > I am connecting to a 4D database via ODBC in a vb6 application I have a
> > problem querying the memo fields from the database (in
> > 4d their called text fields, but are the same type as an access memo
> > If I query using ado, all the memo fields are returned as null. I can
> > the memo fields using dao , but I can bind any controls to the
> > Does anyone have any suggestion as to how to correct the problem using
> > or dao?
> > Haim Katz