255 character limit

lame_designer

Registered User.
Local time
Yesterday, 22:25
Joined
Jan 31, 2006
Messages
14
In my form I have a combo and it is bound to a table. When select an item in the combo I a standard letter should show up in a textbox. The letter has over 500 characters. The problem that I encounter is that the textbox seems to be limited to 255 characters so only half of the letter shows up in the textbox. I did a search on this forum but was not able to solve this problem..

The query in the row-source of the combo = SELECT [Causedby].[Causedby], [Causedby].Description FROM [Causedby];
Width = 3cm;0cm

In the after-update event I used: Me.txtDescription = Me.cmbCausedBy.Column(1)

All tables involved are set to memo.

Can anybody please help ? I'm a bit stuck
 
Last edited:
It sounds to me that your form should be based on a query that combines the table containing the bound field of cmbCausedBy and the table containing the descriptive text. I guess these tables are linked somehow by the value of the bound field of cmbCausedBy.

HTH.
 
Just a thought, have you tried making the TextBox a MemoField? It may not work because I think Access stores MemoFields differently

Col
 
The Causedby and Description fields are in the same table.. I changed both fields to memo (causedby field was set to text, Description was already set to memo) but the problem is still there..
The table I store the textbox data in is also set to memo
 
Last edited:
Are you saying that you're storing the Memo contents in more than one table?
 
Attached is an example in Access 2000 done a bit differently from the method you described but more than 255 characters display in a textbox. I'm not 100% certain of this, but it may be because the form and controls are all bound to a table...

Regards,
Tim
 

Attachments

No, what I am trying to say is that the data is retrieved from 1 table and stored in another..

Thanks alot pono, you might have saved me from a major headache.
will check it out and let you know if I got it working :)
 
Last edited:
lame_designer said:
No, what I am trying to say is that the data is retrieved from 1 table and stored in another..

Then you are duplicating data totally unnecessarily, you only need to store the PK from the first table in the second
 
Rich said:
Then you are duplicating data totally unnecessarily, you only need to store the PK from the first table in the second

Not really, what I'm trying to do is display a default letter which is supplemented with reasons why something is rejected, so it's not like I'm storing duplicates.. It is for a incident reporting database and only 1 item in the combo should display a default text.. problem is we use it for all incidents so it's not like i can break the text appart and only store the supplemented reasons for rejection. Also there is absolutely no room left in my form to add or change the lay-out of the form..

If there is a better way of doing this any help will be appreciated.
 
Last edited:
So if you have a default letter of which the contents don't change and you just add comments then you only need the PK of that field to be able to use it in reports etc. If you want to add further comments then use a subReport which is based on a comments field from another table. As long as the relationships are set correctly it will save a lot of duplication.
 
Thanks Rich, I'll try to figure out if i can implement your suggestions although I'm not sure if I understand what you mean by PK but i do understand your point about double data..

The big problem I have is that I don't really have the liberty to make drastic changes as the form and tables have been in use for a while and everything in it is properly documented in procedures..

Right now we are cutting and pasting a word document in the textbox but only when a certain selection is made in the combo i mentioned.. In all other cases the textbox is a free text field..

Anyway.. thanks for your help guys and will let u know if I figured it out:)
 
pono1 said:
Attached is an example in Access 2000 done a bit differently from the method you described but more than 255 characters display in a textbox. I'm not 100% certain of this, but it may be because the form and controls are all bound to a table...

Regards,
Tim

Pono thanks, your example shows it is possible to show more than 255 characters in a textbox.. but in my case the textbox is bound to a different table so I cannot copy the code 1 on 1.. I feel so stupid, after 2 weeks I still haven't figured it out :(

Regards
 
PK is the primary key for the table which uniquely defines each record so you have one table with like PK which is an auto number and MemoField which stores your longer than 255 char string. In another table you might have a number of different fields and instead of copying the memo field over you can just put the primary key associated with the memo field then create a relationship between the primary key and the new field in your other table so that when access reads 1234544 from that column it knows to pick up the corresponding memo field "Memo field for PK 1234544"
 

Users who are viewing this thread

Back
Top Bottom