Hello, Love this forum. I use Access to interface with our SQL database via an existing project. My host's technician increased the number of characters we can enter in a field. When I cut and paste into the field, it appears on the website as it should. But, when I open that field in Access, it shows me a limited number of charcters then repeats itself from the begining of that field. Different fields show different repeat points and different numbers of characters. But the bigger issue is that I cannot edit the latter part of the field because it is not being shown in Access. Is there something that needs to be changed or reset to allow me to view and edit the entire larger field? Where is the remainder of the text if it is not in the field? I don't know whether he just increased the number of characters or changed to a memo field. Any thoughts?
Increased character field - Problem
- Thread starter MtBob
- Start date
- Local time
- Today, 07:02
- Joined
- Feb 28, 2001
- Messages
- 30,568
A field of type TEXT is limited to 255 characters. Longer text fields must be of type MEMO. If your ORACLE instance is returning more than 255 characters to a TEXT field and the text box happens to allow it, the odds are that you are facing an artifact (bug, ?feature?) of over-sized text boxes.
You should be able to store and edit 65K bytes in a memo field but be aware that such fields cannot participate in primary keys and certain other optimization features.
You should be able to store and edit 65K bytes in a memo field but be aware that such fields cannot participate in primary keys and certain other optimization features.
One field that works fine, is listed as data type ntext 16 and we can put in many, many characters and see it all. But the one listed as nvarchar 4000 truncates the zoomed field. What is the difference between ntext and nvarchar? Would that hinder seeing all the text in the zoom field? Should the fields be memo and not either ntext or nvarchar?
- Local time
- Today, 07:02
- Joined
- Feb 28, 2001
- Messages
- 30,568
Oops, my bad. You said SQL and I read ORACLE. I had just been fighting an ORACLE problem on the time. Had Larry Ellison on my mind, not Bill Gates. (Though one is as bad as the other.)
Access TEXT fields are limited to 255 characters. The equivalent field on your SQL server that is 16 bytes long could be treated as such. But that 4000-byte field has got to be seen as a MEMO field because TEXT fields just can't get that big.
I'll have to defer to those who have SQL Server experience 'cause we don't have one of those here.
Other forumites?
Access TEXT fields are limited to 255 characters. The equivalent field on your SQL server that is 16 bytes long could be treated as such. But that 4000-byte field has got to be seen as a MEMO field because TEXT fields just can't get that big.
I'll have to defer to those who have SQL Server experience 'cause we don't have one of those here.
Other forumites?
I found this in an earlier post:
"Can you check if it runs from the SQL Server???
SQL Server doesn't support 'memo' it'll be varchar or nvarchar."
So the question still remains, why would ntext field allow more than 255 characters and the other nvarchar repeat after 255 characters and not allow us to edit?
"Can you check if it runs from the SQL Server???
SQL Server doesn't support 'memo' it'll be varchar or nvarchar."
So the question still remains, why would ntext field allow more than 255 characters and the other nvarchar repeat after 255 characters and not allow us to edit?
Truncated Fields - My Wife is Going To Kill Me Soon
Please Help. This is causing a terrible problem in that we cannot edit our fields because of this truncating problem. This was not an apparent problem earlier and I do not know what is different to have caused this. What is in the field is not what is online. We can no longer trust that what we see in the database is reflective of what is online. This is killing us.
The Data Type ntext 16 allows us 400+ characters and displays properly, but the nvarchar 4000 truncates the field at 256 characters causing us huge problems. I'm desparate. My wife is having to re-do a huge amount of work because of this problem. Help please. Can we just switch to ntext? What does the 16 mean? How can we put in 400+characters in a 16 field? What is the difference between the nvarchar and the ntext? If we just switch to ntext will it permanently truncate all of our fields?
Please Help. This is causing a terrible problem in that we cannot edit our fields because of this truncating problem. This was not an apparent problem earlier and I do not know what is different to have caused this. What is in the field is not what is online. We can no longer trust that what we see in the database is reflective of what is online. This is killing us.
The Data Type ntext 16 allows us 400+ characters and displays properly, but the nvarchar 4000 truncates the field at 256 characters causing us huge problems. I'm desparate. My wife is having to re-do a huge amount of work because of this problem. Help please. Can we just switch to ntext? What does the 16 mean? How can we put in 400+characters in a 16 field? What is the difference between the nvarchar and the ntext? If we just switch to ntext will it permanently truncate all of our fields?
Similar threads
