ERROR: Field is too large (32K) or View's column & selection formulas are too large

Hi!I just ran an agent on a database to change the form being used by documents. My update was successful, however I noticed that rich-text fields with pasted images (supposedly) in them, display the following error message instead:

ERROR: Field is too large (32K) or View’s column & selection formulas are too large.

What did I do wrong? What can I do to prevent this from happening when I run the same agent on our database in production?

Your help will be greatly appreciated.

Subject: ERROR: Field is too large (32K) or View’s column & selection formulas are too large

When is the error message displayed? When you open the documents?

Are you sure this doesn’t happen even before you run the agent?

I take it your agent just uses formula - please can you post a copy… I’m guessing the problem is not with your agent but with the documents (and not caused by your agent).

Subject: RE: ERROR: Field is too large (32K) or View’s column & selection formulas are too large

Hi Phil! Thank you for your response.Yes, the error message is displayed when I open the documents; at least, those with pasted images in rich-text fields, and the message only appears in these fields. Yes, I’m absolutely sure that this doesn’t happen even before I run the agent.

Below is the code my agent uses:

SELECT @All;

FIELD dToday := @Now;

FIELD oldStatus := SIRStatus1;

FIELD bAssignHide := “False”;

FIELD bAssignClicked := “True”;

FIELD bResolveHide := “False”;

FIELD bResolveClicked := “True”;

FIELD bAuditHide := “False”;

FIELD LifeCycle := @If(@GetField(“SIRStatus1”) = “Unconfirmed”; 1; @GetField(“SIRStatus1”) = “New”; 2; @GetField(“SIRStatus1”) = “Assigned”; 3; @GetField(“SIRStatus1”) = “Reopened”; 4; @GetField(“SIRStatus1”) = “Resolved”; 5; @GetField(“SIRStatus1”) = “Verified”; 6; 7);

FIELD tProj_Name := “PALMS”;

FIELD tSys_Name := SysName;

FIELD SysName := @DeleteField;

FIELD cboList_Stat1 := Status_1;

FIELD Status_1 := @DeleteField;

FIELD tSIR_No := SIR_No;

FIELD SIR_No := @DeleteField;

FIELD tStatus1 := SIRStatus1;

FIELD SIRStatus1 := @DeleteField;

FIELD tBrief_Descript := BriefDescription;

FIELD BriefDescription := @DeleteField;

FIELD cboSeverity := SIRSeverity;

FIELD SIRSeverity := @DeleteField;

FIELD tSRN_Found := SRNNo;

FIELD SRNNo := @DeleteField;

FIELD cboPriority := SIRPriority;

FIELD SIRPriority := @DeleteField;

FIELD cboInstance := TestPhase;

FIELD TestPhase := @DeleteField;

FIELD tTest_Case := TestCaseNo;

FIELD TestCaseNo := @DeleteField;

FIELD rtRelated_SIR := RelatedSIRNo;

FIELD RelatedSIRNo := @DeleteField;

FIELD tPgFrm_Name := PageName;

FIELD PageName := @DeleteField;

FIELD rtHardware := HardwareConfig;

FIELD HardwareConfig := @DeleteField;

FIELD rtSoftware := SofwareConfig;

FIELD SofwareConfig := @DeleteField;

FIELD Author := @Subset(@Author; 1);

FIELD On := “On”;

FIELD rtFull_Descript := DetailedDescription;

FIELD DetailedDescription := @DeleteField;

FIELD cboList_Stat2 := Status_2;

FIELD Status_2 := @DeleteField;

FIELD Assigned_To := AssignTo;

FIELD AssignTo := @DeleteField;

FIELD tStatus2 := SIRStatus2;

FIELD SIRStatus2 := @DeleteField;

FIELD tInstructions := Instructions;

FIELD Instructions := @DeleteField;

FIELD cboResolution := Resolution_1;

FIELD Resolution_1 := @DeleteField;

FIELD cboList_Stat3 := Status_3;

FIELD Status_3 := @DeleteField;

FIELD tResolution := SIRResolution;

FIELD SIRResolution := @DeleteField;

FIELD tStatus3 := SIRStatus3;

FIELD SIRStatus3 := @DeleteField;

FIELD rtResolution_Details := Resolution;

FIELD Resolution := @DeleteField;

FIELD tFiles_Revised := Files;

FIELD Files := @DeleteField;

FIELD tFixTime := ActualTimeToFix;

FIELD ActualTimeToFix := @DeleteField;

FIELD tSRN_Resolved := SRNResolved;

FIELD SRNResolved := @DeleteField;

FIELD dDateSolved := DateSolved;

FIELD DateSolved := @DeleteField;

FIELD tAudit := AuditTrail;

FIELD AuditTrail := @DeleteField;

FIELD FORM := “SIR”;

Subject: RE: ERROR: Field is too large (32K) or View’s column & selection formulas are too large

No problem!

I guess without seeing the form design this might be difficult to nail down. However here are a few ideas:

  1. Check the field types on Form design for the “SIR” form. Check the fields that are causing the error to see what “Type” they are [on the Form design]. Are the fields on the form’s design the same data-type as the fields on the back-end documents? It sounds like maybe you have plain text fields on your form but the fields on your back-end documents contain rich-text. You can check the field types on the back-end document using via document properties from a view.

  2. It may be that the form’s design uses one of the fields’ data in a calculation and it is the calculation that’s causing the error because of the field’s RT content.

Do you know which is the first field on the form that causes the error? If you do then you should look into the design of the field on the form - is it text or is it rich-text? and also, if it isn’t rich text then does it contain any calculations?

If you still don’t get anywhere you can mail me a copy of the design if you want. Please make sure it contains one document that has the problem and one that does not (i.e., one doc that has been updated by the agent and one that has not!). I’ll be happy to have a look at the problem.

Phil Haynes

Subject: RE: ERROR: Field is too large (32K) or View’s column & selection formulas are too large

Hello again, Phil.1. Yes, all the fields in question are rich-text. A question, though, can you explain to me what “back-end documents” means? Do you mean the documents themselves? I did what you asked me to do (check the field types on the back-end document), and the same fields are also of type rich-text.

  1. There are no fields using the rich-text fields’ data in a calculation. I placed some code in two of the fields’ events, however, but only for inserting a date/time/name stamp in the fields. Yeah, I suppose it would be best if I’d mail you a copy of the design.

Thanks a lot for your help! ü