Query Data Being Truncated

[purceld2]

I have a Query that is truncating the data it obtains from a field in a linked table. The source cell is a memo and the Make-Table Query field is also memo. I think it may be something to do with the " " it has around the data.

This is the source data

"The migration of Broadband, Braodband Talk and VAS products from the legacy stack (SMART/CSS) to the customer centric platform (Oneview / Geneva). Swordfish is made up of the following phases:
Swordfish Ph1b - HIT voice channel
Swordfish Ph2b - HIT online & voice channel completion
Swordfish Ph2c - VAS on SDP
Swordfish Ph3b - DV & NP on CCP
Swordfish Ph4 - VAS migrations to CCP
Now includes CPN500 VAS Migrations to CCP"

This is the data retrieved by the query

'"The migration of Broadband, Braodband Talk and VAS products from the legacy stack (SMART/CSS) to the customer centric platform (Oneview / Geneva). Swordfish is made up of the following phases:

Swordfish Ph1b - HIT voice channel

Swordfish Ph2b - HIT onl

It seems to have added a Single quote at the begining

Does anybody know how to solve this problem.

Thanks in advance

 

[dkinley]

Not sure off the top of my head but stuck the return into Word. According to the word count there are 255 characters. I know that is the limit for text fields but don't know why it would do it if a make table.

Here is something I found doing a quick search. Just an explanation on the limit of when processing memo data - no assistance or workaround.

http://allenbrowne.com/ser-63.html

-dK

 

[purceld2]

I know, but I have checked all the fields they are Memo not text

 

[purceld2]

For information

When an application called Oracle Discoverer is used to retrieve data from the same tables there are no problems.

 

[dkinley]

I would assume from the link that for processing of the memo field in the instance you want to use it that the system could use a variant in order to accomplish the task. Based on this assumption (and I am definitely assuming) I am not sure if there is a quick workaround or what it would be. The one in my head that I would imagine would be very convoluted and probably not work

I would dig into Allen Browne's site to see if there is something there unless someone else has overcome this problem before and can help out.

-dK