I have a form with a memo field. This field is based on a table with a field set as a memo data type. The problem is that although the form field lets you type endlessly, it only saves 255 characters. A memo field is supposed to let you enter up to 64000 characters. Has anyone else ever had this problem, if so what was the solution?
I am in the process of changing over a text field to a memo field to generate more space (in 5 different databases :eek: ) Thanks to all the good info on several searches of this forum, I am pretty clear on how to do that.
The question is... when I convert a field that already has information in it, will I lose the current information?
when i change records, my subform that has a memo field, shows the memo field data is "highlighted". i can make a mistake and hit any keyboard key and the memo field data will get erased.
is there a way to prevent such a problem?
if not, is there a work around. eg, hide the memo field until needed for more input? ideas on both issues?
I have a unbound textfield which is defined as a MEMO as i need the capacity the memotype gives. When i use DLookup to retrieve text from a tablefield it seems like the DLookup function can't retrieve all the text from it. The capacity is there when i use bound relations (not using DLookup), but not with it. Does anyone know how i can get around this?
Can a combo box, used to auto fill fields on a form, use a memo field? My selections seem to be cutting off at the 255 character limit, eventhough the underlying table is set to memo field. Is there a work-around for this issue?
My website keeps going down. We run an Access database with ASP coding. I have been told that the problem is from Access having limitations. I read in another posting here that there is a limit of 255 concurrent users, something that we would reach.
I want to know what is the best way forward. Would I need to upgrade to MS sequel? Could I switch to MYSQL? What is the best option and how would I go about doing it? Any other tips or pointers would be much appreciated.
I have created one to many relationships for each of 10 cascading tables dependent on related records in each preceeding table and was expecting to be able to drill down into them in the standard database window prior to creating a data access form to work with.
However i have found that tables 1 through 7 are visible, but access doens't give a little "+" in the corner of table 8 to get to tables 9 and 10. i.e, i can't seem can't seem to drill down beyond table 8 to view related records in tables 9 then 10.
Does this mean that there is a limit to how far you can drill down through table relationships within access?
I have created one to many relationships for each of 10 cascading tables dependent on related records in each preceeding table and was expecting to be able to drill down into them in the standard database window prior to creating a data form to work with.
However i have found that tables 1 through 7 are visible, but access doens't give a little "+" in the corner of table 8 to get to tables 9 and 10. i.e, i can't seem can't seem to drill down beyond table 8 to view related records in tables 9 then 10.
Does this mean that there is a limit to how far you can drill down through table relationships within access?
I just had a couple quick questions. My first question is access limited to a certain amount of records per table, or limited on how big (disk space wise) a database can be. The reason why I asked was I think I read access 97 had a limitation on the db could be no more then 2 gigs, or so many records per table, or both.
My office gave me assignment to find out the scope & limitations of the two Microsoft database applications - MS Access and MS SQL Server. After the findings, we have to chose the more appropriate database for our new project, which will have a humble start but may grow big in a year or two.
I will apreciate the info in facts & figures (not only in general).
We are planning a database application for a client that will need to be accessed remotely by their consultants. We will initially host this application on one of our servers for a few months, and then the client will take it over and host it. The problem we are facing is that this client wants to use ms access as the database, and doesnt want the interface to be web based. The plan was to use data access pages, and let their consultants use a remote desktop connection to access these pages. I don't use access, but I was under the impression that access couldn't really support multiple users hitting the database in this format. Is this correct?
DoCmd.OutputTo to export a query but this truncates the memo fields, but in the db window,right clicking and choosing to export does not truncate the data.
How do I code to output all the data without truncating?
I have a txt box on a report which should show comments.. In the background table the field this txt box is bound to has a data type of memo. Yet the txt box on the report stops showing any more than 255 characters! any clues? I know 255 is the field size set for my Txt fields but memo fields should be able to display 65000000000000000 trillion characters with no problems.
When I look at the table the memo field has all the txt in it, it just wont display all the txt on the report.
Are there any other advantages in using a text field verses a memo field other than memory allocation? Memory allocation seems like such a small issue these days.
I need to take out the carriage returns but keep the items delimited in some way so they all apear on the one line. These are the child parts for kits so i need to keep them on one line as i import them or via a query so i can see the parent part they belong to.
If I read the documentation then memo field in a Access table can be 65.000 chars long. I have three memo fields in a linked ODBC table which is filled by a append query from SQL-server database. The text in these field is cut off by 255 chars. Does somebody know what the cause of this can be?
1. Is there a limitation/property where I can configure the length of Access memo field? DAO? I have read something about this but I don't understand this.
2. How can I trace that everything is send from the source? Maybe it's cut off at the source site. On this moment I don't know something about a Linked tabel. Is there a sniffer or trace tool so that I can see what kind of data is realy send?
Let me say first I am a novice Access user, just trying to teach myself a few things to make my job easier. So take it easy on me with any feedback.
This is my situation. I am using a web based help desk ticketing software that has an Access DB. I have created a couple of queries and linked them together that seem to be working and giving me the data that I want with one exception.
I am tring to query a memo field, which is the description of a ticket, and the output is only a small portion of what is actually entered in to the table. Is there a way either in my query or report builder to make a change that will output all of the data from the description field?
A couple of things that I've tried on my own are to change the data type for that field from memo to text, however that that puts limits on the amount of data that can be entered in and causes the help desk software to function incorrectly. I've also turned on Can Grow and Can Shrink for the text box for the output in my form.
Any help you can offer would be greatly appreciated.
Ok, firstly i have search google and this forum from top to toe and no-1 has an answer that works for me.
I am running a query, now i have completely simplified it. The query is now just picking up a field called recommendations. Recommendations is a memo field with no formating or index on at all. Now, when i run the query as normal it works fine... everything is there. But when i have to group by it. It cuts it off at 255 charactors. The thing is i need to do some sums and counts within the query aswell so it has to be.
I have checked microsoft and there suggestions are not any use.
I have a form set up where user's type in an explanation of how a claim is being appealed and resolved in a memo field.
One problem, for some reason management doesn't want these explanations to end with a period. But the users keep ignoring our request and keep using the period.
Is there a way that you can code this memo field to where it will allow punctuation throughout, except at the end?
Hello All... I've got an address multi-line field in my form. The user types his 1st line of address in the field, presses enter, types the 2nd line of the address, presses enter & so on....And submits the form. The problem is only the 1st line is uploaded into the access database. The field is a memo data type. Can anyone help me with this problem? Cheers...
I'm using an append query to add a new record from a form. The form has a text box and the contents get entered into a Memo field in the database. When I put more than 100 chars in the textbox and try to save to the database I get an "Invalid Argument" error.
If I use less than 100 chars then it appends fine. The error doesn't come from the textbox, I can put over 100 caracters in that, the error comes from the Append process.
In the append query I use this string. Expr13: [forms]![additem].[description]
additem is the form description is the textbox field.
i am using a memo field in a table that is being used in a form as a combo box.when i use the combo box drop down the form is only bringing in the first 255 characters of the memo field, how can i change this?
i am using a memo field in a table that is being used in a form as a combo box.when i use the combo box drop down the form is only bringing in the first 255 characters of the memo field, how can i change this?