Truncating memo field

  • Thread starter Thread starter Tamara
  • Start date Start date
T

Tamara

I have read through the posts on why a memo field truncates and can't seem to
find any of the possible reasons. Here is my query:
-----
SELECT [Portfolio List].[PRISM ID], Import_All_Project_Statuses.[TARGET
END], Import_All_Project_Statuses.[CURRENT PHASE], Left([Status Details],1)
AS Overall_Status, Mid([Status Details],InStr([Status Details]," ")+2) AS
Overall_Details INTO RawData_ProjectStatus
FROM [Portfolio List] LEFT JOIN Import_All_Project_Statuses ON [Portfolio
List].[PRISM ID] = Import_All_Project_Statuses.ID;
 
If you run your query as just a SELECT query is the data in the memo field
truncated? Since you did not tell us WHICH field is being truncated it is hard
to guess why.

Something to try:
Instead of using a make table query, create the table first and define the
memo field as a memo field. Then use an append query to add the records to
the table. It could be a bad guess on what field type is needed - text or
memo based on who knows what algorithm.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
 
Mybad...of course you need to know which field is truncated. The query
splits the original field (Status Details) into two target fields (Overall
Status which contains the first word and Overall Details which contains the
rest of the field). Overall Details is the field that is truncated.


John Spencer said:
If you run your query as just a SELECT query is the data in the memo field
truncated? Since you did not tell us WHICH field is being truncated it is hard
to guess why.

Something to try:
Instead of using a make table query, create the table first and define the
memo field as a memo field. Then use an append query to add the records to
the table. It could be a bad guess on what field type is needed - text or
memo based on who knows what algorithm.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
I have read through the posts on why a memo field truncates and can't seem to
find any of the possible reasons. Here is my query:
-----
SELECT [Portfolio List].[PRISM ID], Import_All_Project_Statuses.[TARGET
END], Import_All_Project_Statuses.[CURRENT PHASE], Left([Status Details],1)
AS Overall_Status, Mid([Status Details],InStr([Status Details]," ")+2) AS
Overall_Details INTO RawData_ProjectStatus
FROM [Portfolio List] LEFT JOIN Import_All_Project_Statuses ON [Portfolio
List].[PRISM ID] = Import_All_Project_Statuses.ID;
Click to expand...
Click to expand...
 
I tested your suggestion on creating the table then using append. Works
great after creating/running a delete query first.

John Spencer said:
If you run your query as just a SELECT query is the data in the memo field
truncated? Since you did not tell us WHICH field is being truncated it is hard
to guess why.

Something to try:
Instead of using a make table query, create the table first and define the
memo field as a memo field. Then use an append query to add the records to
the table. It could be a bad guess on what field type is needed - text or
memo based on who knows what algorithm.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
I have read through the posts on why a memo field truncates and can't seem to
find any of the possible reasons. Here is my query:
-----
SELECT [Portfolio List].[PRISM ID], Import_All_Project_Statuses.[TARGET
END], Import_All_Project_Statuses.[CURRENT PHASE], Left([Status Details],1)
AS Overall_Status, Mid([Status Details],InStr([Status Details]," ")+2) AS
Overall_Details INTO RawData_ProjectStatus
FROM [Portfolio List] LEFT JOIN Import_All_Project_Statuses ON [Portfolio
List].[PRISM ID] = Import_All_Project_Statuses.ID;
Click to expand...
Click to expand...
 
Back
Top