Cotswold
Active member
- Local time
- Today, 01:57
- Joined
- Dec 31, 2020
- Messages
- 649
In the olden days using dBASE Tables I experienced errors and sometimes corruption using the somewhat strangely named MEMO type fields in Tables. After I removed all of the MEMO fields from the dBASE tables the problems went away. When I moved to Access I then tried the Memo field in the .MDB and within a year had similar errors. Again, that could have been flaky networks, or even users switching off the PC instead of closing down. But I didn't have the time or inclination to prove it. So I took the lazy doctors' solution of treating the symptoms and not the causes. I removed the Memo fields from the .MDB and no more issues. So on this very tiny statistical analysis I have avoided Memo fields in everything Access. I will add that the issues I had were in .MDB databases. Maybe the .ACCDB are an improvement in this regard?
I am developing an application in Access2019 and using a LongText field in a main table would be an easy solution for me. The maximum number of records in any single table I expect to be in the range of 1,000 to 5,000 so quite small really. In just one table maybe 40% of the records would have text of varying lengths in a LongText field. This would be from five or six lines, up to to maybe the contents of one and at the most three A4 pages. Whilst in the other 60%, the LongText field I'd expect to be empty. I could have a separate Table containing the LongText, but my preferred design is in in the main table.
My opinion at the moment is don't use them.......just in case it give me problems later. However, as it is possible that I'm the only Access user in the World who doesn't use them, and as I say, I'm in search of an easier solution. I am wondering what the broader experience is at Access-Programmers with the LongText and what your opinion is on the use of the LongText Fieldtype?
Do you avoid them, or do you use them all the time without any hesitation, or issues?
I am developing an application in Access2019 and using a LongText field in a main table would be an easy solution for me. The maximum number of records in any single table I expect to be in the range of 1,000 to 5,000 so quite small really. In just one table maybe 40% of the records would have text of varying lengths in a LongText field. This would be from five or six lines, up to to maybe the contents of one and at the most three A4 pages. Whilst in the other 60%, the LongText field I'd expect to be empty. I could have a separate Table containing the LongText, but my preferred design is in in the main table.
My opinion at the moment is don't use them.......just in case it give me problems later. However, as it is possible that I'm the only Access user in the World who doesn't use them, and as I say, I'm in search of an easier solution. I am wondering what the broader experience is at Access-Programmers with the LongText and what your opinion is on the use of the LongText Fieldtype?
Do you avoid them, or do you use them all the time without any hesitation, or issues?