And because the updated record ends up in a different place from the original record, you will see records out of place (based on PK sequence) if you don't specifically sort a recordset
This is a big disadvantage and is the reason I avoid using rich text in them. You can search in them as long as they just have plain text.
So after all of the above digging into the workings of long text fields, what is the ultimate conclusion? Do they still cause problems or not? It appears like most of us don't see an issue with them anymore but just wanted to confirm.
This is a big disadvantage and is the reason I avoid using rich text in them. You can search in them as long as they just have plain text.
So after all of the above digging into the workings of long text fields, what is the ultimate conclusion? Do they still cause problems or not? It appears like most of us don't see an issue with them anymore but just wanted to confirm.
Sorry my answer was incomplete. I should have said that queries will often truncate memo fields at 255 characters therefore limiting their usefulness when filtering
In fact, you can search long text fields with rich text by filtering on a PlainText version of the field:
Code:
SELECT tblRichText.ID, tblRichText.Details, PlainText([Details]) AS PlainTextDetails, tblRichText.Details AS HTMLDetails
FROM tblRichText
WHERE (((PlainText([Details])) Like "*text with*"));
The screenshot shows the query results & part of the original table
I often use the PlainText function to allow me to search rich text memo fields
So the PlainText method strips out the actual text from the html? That's a great idea as long as it doesn't slow things down. Opens up some possibilities now. I just looked that up and sure enough that option is available.
No, the plain text function doesn't cause any noticeable slowdown even when the record is very large & the formatting is complex
And in answer to your earlier question, I have no issues about using long text / memo fields
I use plaintext/richtext instead of conditional formatting on continuous forms where it is much faster.
Note you can apply richtext to form/report textbox controls, even if the controlsource is a short text field
Does mean that when viewed in the table the short text will look like as shown in Colin's post #23 - or you apply the formatting code in the form recordsource.