How do I exceed 255 char limit when exporting calc'd field to .txt

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I can export an access query to a text file with no problem. This includes
exporting one large text blob field - where some records exceed 350 chars in
width

However, if I change the query to include a calculated field that combines
two fields from a table together (i.e. the original text blob of 350+ chars,
and one more field of about 50 chars), then I get problems exporting to a
text file: the resulting text file is truncated so that the calcuated field
is a max of 255 chars wide. (i.e. it is now shorter than if I just exported
the original text blob)

I can see all characters in the access query - it is the exporting process
that truncates it

Anyone know why this happens? (and more importantly how to get around it)

TIA
 
Just to add a bit more info: the original text blob is "memo" format, not
text.

What I am trying to do is move a bulletin board from one server to another
bbs package on a different server. The "memo" formatted field contains the
bulletin board messages. I am trying to pre-pend a html link to each message
so that users can go from the new bulletin board back to the original.

The calculated query field goes something like expr1:
"http://oldbbs.com/message/"&[message_num]& "<br />" & [message]

When I look at the query table, everything is ok - I see the link and the
full text of the message contained in the one field. When I export to text,
then I lose everything after 255 chars. Weird

Help please.
 
You don't say how you're exporting the data. Possible reasons:

(1) OutputTo will truncate long strings. Use TransferText for text file,
TransferSpreadsheet for EXCEL file.

(2) When you export the results of a query to a text file or an EXCEL
spreadsheet, all calculated fields within that query will truncate their
strings to 255 characters. See this Knowledge Base article:

Exported Query Expression Truncated at 255 Characters
http://support.microsoft.com/default.aspx?scid=kb;en-us;207668

Workaround would be to create a temporary table for the data, append the
query's records to this temporary table, export the temporary table, and
then delete the temporary table.
 
Back
Top