By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,991 Members | 1,888 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,991 IT Pros & Developers. It's quick & easy.

Memo Size limit different on each workstation?

P: 9
When a user attempts to past around 30,000 characters of text into a memo field the user gets a size limit error of some kind; however when I past the same data from my workstation into the memo field the data populates just fine. We also have the exact same T42 IBM thinkpad and the verision of access is the same on both workstations. Any ideas as to what's causing this?
Mar 8 '07 #1
Share this Question
Share on Google+
7 Replies


ADezii
Expert 5K+
P: 8,619
When a user attempts to past around 30,000 characters of text into a memo field the user gets a size limit error of some kind; however when I past the same data from my workstation into the memo field the data populates just fine. We also have the exact same T42 IBM thinkpad and the verision of access is the same on both workstations. Any ideas as to what's causing this?
My guess would be that one of you, (the one getting the error), has Unicode Compression set to NO for this Memo Field. This logic would seem correct since Unicode represents a character as 2 Bytes instead of 1 and the limit for a Memo Field is 65K plus.
__1. Open the Table in Design View.
__2. Select the Memo Field.
__3. Click on the General Tab and make sure that Unicode Compression is set to Yes.
Mar 9 '07 #2

P: 9
My guess would be that one of you, (the one getting the error), has Unicode Compression set to NO for this Memo Field. This logic would seem correct since Unicode represents a character as 2 Bytes instead of 1 and the limit for a Memo Field is 65K plus.
__1. Open the Table in Design View.
__2. Select the Memo Field.
__3. Click on the General Tab and make sure that Unicode Compression is set to Yes.

Thanks very much, this resolved our issue! I'm a little confused though how it worked for one user and not another user even though they are accessing/utilizing the same access application.
Mar 9 '07 #3

NeoPa
Expert Mod 15k+
P: 31,347
Thanks very much, this resolved our issue! I'm a little confused though how it worked for one user and not another user even though they are accessing/utilizing the same access application.
That's a good question.
You're both using the same front-end database file?
Is the table you're pasting into linked or native in your FE database?
Mar 10 '07 #4

missinglinq
Expert 2.5K+
P: 3,532
And to confuse things even more, I have memofields with Unicode Compression set to NO with 40-50k characters and no problem with truncation! Ain't Access grand!
Mar 10 '07 #5

NeoPa
Expert Mod 15k+
P: 31,347
I'm guessing, from what you just said Linq - and what the OP experienced, that there's some sort of situation where Unicode Compression is used even in circumstances where it's not explicitly set. Hence the same situation working differently on their two machines. I would have no idea what that could be though, I'm afraid.
Mar 10 '07 #6

missinglinq
Expert 2.5K+
P: 3,532
As the father on The Waltons used to say "Life's a mystery!"
Mar 11 '07 #7

NeoPa
Expert Mod 15k+
P: 31,347
Well, Ain't that the case John Bawy.
Mar 11 '07 #8

Post your reply

Sign in to post your reply or Sign up for a free account.