DataMystic

Possible. I got my problem solved by using the OpenOffice.org Database to retrieve the full memo fields. I think they have their own MS Access connection instead of the ODBC I use with TexPipe.

best regards,
Christian

If I understand your answer correctly, there is no way to handle memo fields larger than 255 characters in length with TextPipe and that's it.
Bottomline what you say is: look at another SW to do that. Tell me I did not get your message correctly.

Christian

Well apparently my workaround does not work if data is really more than 255 characters. I'm stuck!

Christian

In the meantime I found the following (clumpsy) workaround: instead of using left(MyField, 500) use: mid(MyField,1,250), mid(MyField,251,500) (add more if needed) And then use a filter to put the separate fields back in one field by restricting on those fields and removing the field delimiters and t...

TextPipe current version: 7.6.3 Sorry had other priorities. Finally here is an answer on your question: the field is a memo field. I come back on it because there is another odd problem with this type of data. Besides the "Error-Invalid variant operation" problem, if I use my workaround it...

I just updated TextPipe Pro from 7.0.something to 7.4.2 and I am getting an "Error-Invalid variant operation" which I did not get with previous version. The filter is getting data out of an Access DB with an SQL statement in the trial run area. I could solve the problem by changing SELECT ...

I need to select data from 2 data bases.
Special filter > DataBase connection seems to only accept one database.
Any way it can be done in a single TextPipe filter?

thanks,

Christian

I receive 'BLOB' as a result of a 'count(status)' in my SQL select statement. TextPipe's Help says to try to use a subfilter with 'mime base64 encoding', I tried many of the possible encoding choices finally I got my result just using 'SUBSTRING(count(status),1,100)' instead of the 'count(status)'. ...

And if it gives date and time, maybe it's not a good idea to call it @today, it may be better to call it @now or @timestamp.

christian

I don't really care about the format because textpipe's filters can be used to reformat to whatever is needed.
I would suggest something like YYYY-MM-DD HH:MM:SS

christian

Currently 3 macros available (@inputfilename, @fullinputfilename and @clipboard).
What about a macro to insert current date and time? Something like : @today?

christian