473,396 Members | 1,895 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,396 software developers and data experts.

"The field is too small to accept ..." error for a bound control on a form

Hello,
I've posted this problem to one other newsgroups, and gotten
some diagnostic help, but I still need a solution. The full text of
the message box is: "The field is too small to accept the amount of
data you attempted to add. Try inserting or pasting less data". This
displays without a run-time error number.
This error comes about when a user (I've been able to reproduce
this error on 2 different workstations; one running
Access2000/Windows2000 and one running Access97/NT4) tries to edit a
9-digit field, defined as such, in the field of the table to which
this control is bound. What is really strange is this:
1) The control (a text box) has no problem containing the data if it's
being displayed and not edited (user has to click a button to edit
data on the form; said button is disabled for users in the
Inquiry-Only group);
2) Another form I have that has the user input data into this form (on
this form, it's intake, so data is ALWAYS being added), has NO trouble
whatsoever with inputting 9 digits; saves it without complaint;
3) I have tried a couple of diagnostic message boxes in BeforeUpdate
for the control that is giving me the problem (on the update form),
and both verify that I am only attempting to input 9 characters.
4) I printed out a KB article for this problem, but it doesn't provide
a solution, as I am not going beyond the number of characters
specified for this field.
Please advise, thanks. F.Barth
Nov 12 '05 #1
5 10176
What number was the kb article?

The field you refer to that contains a 9-digit number: what is the data type
of the field? Text or Number? And what is the Field Size (lower pane in
table design view)?

It may be possible to trap this error in the Form_Error event. However,
that's not going to tell you much more than you already know.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"F. Barth" <Is*******@hotmail.com> wrote in message
news:6b**************************@posting.google.c om...
Hello,
I've posted this problem to one other newsgroups, and gotten
some diagnostic help, but I still need a solution. The full text of
the message box is: "The field is too small to accept the amount of
data you attempted to add. Try inserting or pasting less data". This
displays without a run-time error number.
This error comes about when a user (I've been able to reproduce
this error on 2 different workstations; one running
Access2000/Windows2000 and one running Access97/NT4) tries to edit a
9-digit field, defined as such, in the field of the table to which
this control is bound. What is really strange is this:
1) The control (a text box) has no problem containing the data if it's
being displayed and not edited (user has to click a button to edit
data on the form; said button is disabled for users in the
Inquiry-Only group);
2) Another form I have that has the user input data into this form (on
this form, it's intake, so data is ALWAYS being added), has NO trouble
whatsoever with inputting 9 digits; saves it without complaint;
3) I have tried a couple of diagnostic message boxes in BeforeUpdate
for the control that is giving me the problem (on the update form),
and both verify that I am only attempting to input 9 characters.
4) I printed out a KB article for this problem, but it doesn't provide
a solution, as I am not going beyond the number of characters
specified for this field.
Please advise, thanks. F.Barth

Nov 12 '05 #2

"F. Barth" <Is*******@hotmail.com> wrote in message
news:6b**************************@posting.google.c om...
Hello,
I've posted this problem to one other newsgroups, and gotten
some diagnostic help, but I still need a solution. The full text of
the message box is: "The field is too small to accept the amount of
data you attempted to add. Try inserting or pasting less data". This
displays without a run-time error number.
This error comes about when a user (I've been able to reproduce
this error on 2 different workstations; one running
Access2000/Windows2000 and one running Access97/NT4) tries to edit a
9-digit field, defined as such, in the field of the table to which
this control is bound. What is really strange is this:
1) The control (a text box) has no problem containing the data if it's
being displayed and not edited (user has to click a button to edit
data on the form; said button is disabled for users in the
Inquiry-Only group);
2) Another form I have that has the user input data into this form (on
this form, it's intake, so data is ALWAYS being added), has NO trouble
whatsoever with inputting 9 digits; saves it without complaint;
3) I have tried a couple of diagnostic message boxes in BeforeUpdate
for the control that is giving me the problem (on the update form),
and both verify that I am only attempting to input 9 characters.
4) I printed out a KB article for this problem, but it doesn't provide
a solution, as I am not going beyond the number of characters
specified for this field.
Please advise, thanks. F.Barth

Nov 12 '05 #3
I've run into this problem before -
getting that diagnostic message when it turned out that something quite
different was actually the problem.
Wish my memory were better!!
First thing I'd guess would be corruption -
are you familiar with ways to address that?

= Turtle

"F. Barth" <Is*******@hotmail.com> wrote in message
news:6b**************************@posting.google.c om...
Hello,
I've posted this problem to one other newsgroups, and gotten
some diagnostic help, but I still need a solution. The full text of
the message box is: "The field is too small to accept the amount of
data you attempted to add. Try inserting or pasting less data". This
displays without a run-time error number.
This error comes about when a user (I've been able to reproduce
this error on 2 different workstations; one running
Access2000/Windows2000 and one running Access97/NT4) tries to edit a
9-digit field, defined as such, in the field of the table to which
this control is bound. What is really strange is this:
1) The control (a text box) has no problem containing the data if it's
being displayed and not edited (user has to click a button to edit
data on the form; said button is disabled for users in the
Inquiry-Only group);
2) Another form I have that has the user input data into this form (on
this form, it's intake, so data is ALWAYS being added), has NO trouble
whatsoever with inputting 9 digits; saves it without complaint;
3) I have tried a couple of diagnostic message boxes in BeforeUpdate
for the control that is giving me the problem (on the update form),
and both verify that I am only attempting to input 9 characters.
4) I printed out a KB article for this problem, but it doesn't provide
a solution, as I am not going beyond the number of characters
specified for this field.
Please advise, thanks. F.Barth

Nov 12 '05 #4
The KB article was 121512. The specific problem I have with it is
that it says that the error is caused if one field in a record has a
default value that is too large for the field's size. However, my
users are able to change other fields using that same (update) form.
This error has only been reported on one field. So if there was a
problem with a default value on another field, then this error would
be occurring much more frequently.
The field in question is defined as Text, 9.
F. Barth
Nov 12 '05 #5
Okay. The k.b. does not apply, and you are fairly certain which field causes
the problem, because you can create the problem by editing *only* this field
on your form.

Is there anything in the Format or Input Mask properties of the text box
that could be masking what is really there? Or a Validation Rule? Anything
in the BeforeUpdate or AfterUpdate events of the text box?

While the text box has been edited and the record cannot be saved, are you
able to move focus to another text box? If so, open the Immediate window
(Ctrl+G) and ask Access how long the field is. Something like this:
? Len(Forms![Form1]![Text1])

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"F. Barth" <Is*******@hotmail.com> wrote in message
news:6b**************************@posting.google.c om...
The KB article was 121512. The specific problem I have with it is
that it says that the error is caused if one field in a record has a
default value that is too large for the field's size. However, my
users are able to change other fields using that same (update) form.
This error has only been reported on one field. So if there was a
problem with a default value on another field, then this error would
be occurring much more frequently.
The field in question is defined as Text, 9.
F. Barth

Nov 12 '05 #6

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Mark | last post by:
Hi, I'm running visual studio 2003, and am now receiving the error "The Operation Could Not Be Completed" when attempting to add a form / control or component class to a project. I can add any...
6
by: TS | last post by:
Hi, i have a problem validating xml against schema. I used http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx validator and it says it is fine. Can you tell me why this doesn't work? ...
1
by: RWC | last post by:
Hello, I'm getting the error "The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data" when I run a report. I'm simply trying to apply the...
12
by: Yarco | last post by:
when doing fork in a loop: while(1) { tmp_sd = accept(sd, (struct sockaddr*)&tmp_sin, &len); if (tmp_sd == -1) { perror("accept"); exit(0); } //check client ip
8
by: Lars-Erik Aabech | last post by:
Hi! We've got an ASP.NET application that runs swell on development PC's and one live production server. Another prod. server though crashes a couple of times a week. Either something that...
0
by: davidr | last post by:
Hi, I have a panel that I load user Control in no problem. The problem arrises when I do a post back on one of these user controls. I have button it does a click event. In this click event I...
7
by: PW | last post by:
Hi, I have a form with unbound fields on it. The user selects a record from a recordset and I populate the unbound fields. When I try to change the unbound quantity text box, Access 2003 tells...
9
by: Ecohouse | last post by:
I have a main form with two subforms. The first subform has the child link to the main form identity key. subform1 - Master Field: SK Child Field: TrainingMasterSK The second subform has a...
10
by: Roger | last post by:
ms-access97 & sql server2005 two tables tblItem tblItemFeature form frmItem contains subform frmItemFeature each form is based on their respective table creating new record and filling in...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
by: emmanuelkatto | last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud. Please let me know. Thanks! Emmanuel
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
0
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
0
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers,...
0
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
0
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
0
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.