On Nov 5, 9:10 pm, "Allen Browne" <AllenBro...@SeeSig.Invalid> wrote:
> How are you exporting the data?
>
> If you OpenRecordset and loop through the data, it could be this issue:
> Concatenated fields yield garbage in recordset
> at:
> http://allenbrowne.com/bug-16.html
>
> If the query truncates, it could be this:
> Truncation of Memo fields
> at:
> http://allenbrowne.com/ser-63.html
>
> If the query contains a GROUP BY clause, it could be this:
> Grouping by Memo field yields garbage
> at:
> http://allenbrowne.com/bug-18.html
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users -http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Curmudgeon" <eht...@gmail.com> wrote in message
>
> news:37c30b06-21b3-4e2f-a677-(E-Mail Removed)...
>
> >I have a table with several memo fields that display the entered data
> > correctly; queries on the table also display the returned data
> > correctly. I can copy and past the data from the fields into notepad,
> > and it displays there correctly as well.
>
> > However, when I write the data to a text file (Print #1, qry!
> > [FieldName]) the first 255 characters are rendered correctly, but all
> > characters beyond 255 are garbled (question marks, undefined
> > characters such as ANSI 0, 1, [Space] 32, and a couple of stray alpha
> > characters).
>
> > I have used this technique in other applications for many years with
> > no problem, and this one is stumping me.
>
> > Any suggestions?
>
> > Thanks
> > Dave
Allen,
While the problem was not exactly as described in your pages, I
examined my queries and found that calculations being done on the memo
fields were causing the truncation; apparently due to some Jet quirk
the text in excess of 255 characters gets passed on, but with
incorrect character codes.
I am now using my query to append the records to a temp table, which
then serves as the recordsource for my code - works like a charm.
Thanks for the suggestions!
Dave
Similar Threads
