Apr 6 2006, 01:33 PM
I've searched the internet several times on this subject and my problem doesn't seem to fit the scenerios I'm seeing. I have a data entry form - the first field (is populated with a serial number which will be the primary key to the record being added). That field is visible but with no tab stop. The first field the user can use is a combo box which is populated from a table that has a 2 character ID and a 15 char description. The field in the record that will be added is also set at 2 character size. The combo box is bound to the field in question (used the wizard). Everytime I try to choose from the drop down, I get 'The field is too small to accept the data you attempted to add." message. On clicking Help, it shows error #3163.
I've triple checked the field sizes and the size of the column widths properties (I show both fields to the user). I've even tried dropping the field from my form - when I do the next field in line gives me the same error. Would that indicate a totally different problem, like a bad join?
I don't know what else to try. I'm not dealing with large fields here but everything I find on the internet seems to be dealing with large fields.
Apr 6 2006, 01:55 PM
My first thought is that combo box is bound to the description and not the ID. If this is true is will try to place the 15 char description into the 2 char Id. This would generate the too small error.
Apr 6 2006, 01:58 PM
Make sure the data types match first. then make sure the combo is using the correct bound column in its properties. If you used the wizard then it probably made column 1 the bound column. Make sure column one in the underlying query in the combo is correct for what you want.
Apr 6 2006, 02:00 PM
the first field (is populated with a serial number which will be the primary key to the record being added).
The primary key should NOT be the serial number. The serial number should be a second key
I have found that using the "serial number" or anything that is not system assigned as a primary key will cause other issues in the future.
Apr 6 2006, 02:12 PM
My first thought, too. But the ID (2 char field) is the first field and that is what column the property is set on (set by the wizard). I even tried not to include the description field - to only include the ID and I still get the same error. Thanks for trying though.
Apr 6 2006, 02:16 PM
Everything seems to be correct - all fields involved are Text fields. The first field in the table populating the combo box is a 2 char text and the field in the table I'm adding records to is a 2 char text. The bound column property says 1 - should work. Thanks for trying though.
Apr 6 2006, 02:19 PM
I understated about my primary key - the primary key (and the first control showing in my form) is a combination of a leading letter and a next available number from a separate 'serial' number table - where each type of transaction has a different 'next available number'. Nothing wrong with that, right? I've got at least a half dozen tables that I'm using such a key - and no problems with those - thus far.
Apr 6 2006, 02:32 PM
I should mention that after I receive the error message and click OK, I can then select a value and move on.
Apr 6 2006, 03:51 PM
Not to be a big pain - but it's kinda weird, if I tab past the problem field without an entry and then backtab back to it - it doesn't give me the problem.
Apr 6 2006, 03:54 PM
Don't understand it - but all I changed was to enter a default for the problem field and the problem went away. I wouldn't want anyone to waste any more time on this, but anyone figures it out, I'd sure like to know the answer. Thanx again for all your time.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here