Ms Access Error 3309
108, for a total of 110 - well short of the 255 limit for fields in a table in Access 2003. When I add the second field (no matter what type) and try to save the table, I get an Error 3309 message: 'Property value is too large'. None of the property values are anywhere near 2K, nor have I changed an index property after data was entered. What's even more strange is that part of the information for the second field is saved - name, the type and format - but others such as the validation rule are not. I fear I've found a nasty bug in Access 2003. Can anyone offer help, either for a fix or a work-around? Many thanks. Bill Mathews Bill Mathews, Jul 3, 2007 #1 Advertisements Tony Toews [MVP] Guest "Bill Mathews" <> wrote: >I just added two fields to a table that had 108, for a total of 110 - well >short of the 255 limit for fields in a table in Access 2003. > >When I add the second field (no matter what type) and try to save the table, >I get an Error 3309 message: 'Property value is too large'. > >None of the property values are anywhere near 2K, nor have I changed an >index property after data was entered. > >What's even more strange is that part of the information for the second >field is saved - name, the type and format - but others such as the >validation rule are not. I suspect that the metadata table is larger than one page. What I mean is that there is a table inside the MDB describing your tables. And that the record in that table corresponding to your current table is now larger than the 4 K page size. Or something like that. >I fear I've found a nasty bug in Access 2003. Well, 108 fields in one table is a lot. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Tony Toews [MVP], Jul 3, 2007 #2 Advertisements Guest Guest Hi Bill, Use a form to enter/edit the data and none of this would be an issue in the first place. You've created a multi-step process to accomplish what forms do for a living... I assume you know that already, but it's almost an obligatory reply CW "Bill Mathews" wrote: > I just added two fields to a table that had 108, for a total of 110 - well > short of the 255 limit for fields in a table in Access 2003. > > When I add the second field (no matter w
Links Social Groups Pictures & Albums Members List Calendar Search Forums Show Threads Show Posts Tag Search Advanced Search Find All Thanked Posts Go to Page... Thread Tools Rate Thread Display Modes 07-11-2005, 06:58 AM #1 Geoff tenOever Guest Posts: n/a Property value is too large. (Error 3309) I have developed a Tax Assessment solution using Access 2003, I already have in excess of 150k records, I have 7 tables; 55 queries; 30 forms. My main table "Transact" has over 175 fields (yep I know its large, but I need all these fields and dont want to create 100's of tables). Since last week I cannot save any definition changes to my table, I keep receiving error 3309. I have searched all discussion groups but cannot find any decent http://www.pcreview.co.uk/threads/error-3309-why.3147986/ solution. 1. I have not changed the index's, of no duplicates 2. I do not have more than 255 columns in table 3. I have increased the maxlocks substantially 4. run a compact & repair succesfully What else can I try, as mentioend I am reluctant to split Transact into smaller tables. Regards Gto 07-11-2005, 07:10 AM #2 KenHigg Registered User Join Date: Jun 2004 Posts: 13,295 Thanks: 7 Thanked 155 Times in 129 Posts I would guess you've realized http://www.access-programmers.co.uk/forums/showthread.php?t=89885 a normalization issue. Care to share the table structure, or part of it? __________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. ken “You don’t learn to walk by following rules. You learn by doing, and by falling over.” KenHigg View Public Profile Find More Posts by KenHigg 07-11-2005, 08:15 AM #3 Geoff tenOever Guest Posts: n/a Thanks Ken, silly question , what and how should I send you . Gto 07-11-2005, 08:35 AM #4 KenHigg Registered User Join Date: Jun 2004 Posts: 13,295 Thanks: 7 Thanked 155 Times in 129 Posts Hum... Post something like: MyTableName fieldNameOne fieldNameTwo fieldNameThree . . . __________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. ken “You don’t learn to walk by following rules. You learn by doing, and by falling over.” KenHigg View Public Profile Find More Posts by KenHigg 07-11-2005, 12:06 PM #5 ScottGem Newly Registered User Join Date: Jun 2005 Location: LI, NY Posts: 1,119 Thanks: 0 Thanked 0 Times in 0 Posts Quote: Originally Posted by Geoff tenOever My main table "Transact" has over 175 fields (yep I know its large, but I need all these fields and dont want to create 100's of tables). What else can I try, as mentioend I am reluctant to split Transact into sma
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events https://msdn.microsoft.com/en-us/library/bb209738(v=office.12).aspx Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content you requested has been removed. You’ll be http://www.bigresource.com/MS_ACCESS-Property-value-is-too-large-Error-3309--3j5Nc5g0.html auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office ms access development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Property setting cannot ms access error be larger than 2K. (Error 3309) You are trying to set a property value of an object to a size greater than the largest permissible size of 2K. Shorten the length of the property value. Community Additions Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful? Yes No Additional feedback? 1500 characters remaining Submit Skip this Thank you! We appreciate your feedback. Dev centers Windows Office Visual Studio Microsoft Azure More... Learning resources Microsoft Virtual Academy Channel 9 MSDN Magazine Community Forums Blogs Codeplex Support Self support Programs BizSpark (for startups) Microsoft Imagine (for students) United States (English) Newsletter Privacy & cookies Terms of use Trademarks © 2016 Microsoft © 2016 Microsoft
forms. My main table "Transact" has over 175 fields (yep I know its large, but I need all these fields and dont want to create 100's of tables). Since last week I cannot save any definition changes to my table, I keep receiving error 3309. I have searched all discussion groups but cannot find any decent solution. 1. I have not changed the index's, of no duplicates 2. I do not have more than 255 columns in table 3. I have increased the maxlocks substantially 4. run a compact & repair succesfully What else can I try, as mentioend I am reluctant to split Transact into smaller tables. Regards Gto View Replies Similar Messages: Tables :: Adding Description To A Field - Property Value Is Too Large Error Message Error 3309 Property Value Too Large Property Value Is Too Large Records To Large Error Save Error In Large Table Large Query Aggregate Function Error RecordsetClone Property Error Modules & VBA :: Error - Invalid Reference To The Property Help.. I Got This Error: "an Expression That Has An Invalid Reference To The Property The Notorious Error Message: Can't Set Value To NULL When CheckBox Property = FALSE. ERR: The Expression AfterUpdate You Entered As Event Property Setting Produce Error! Forms :: Expression On Click - Event Property Setting Produces Error One Large Table? Or Two Different Ones? Large Front End Not Much There How Large Can A Query Be? How To Get A Large TXT File Very Large Database, Not Working Large Scale Corruption! Dealing With Large Times Large Database Query Large Database Problems Code Too Large For Procedure Organising Large Database Number Too Large For Field ADVERTISEMENT Tables :: Adding Description To A Field - Property Value Is Too Large Error Message Oct 18, 2012 I keep getting the "Property Value is too large" when I add a description to a field in an existing table. The same error was resolved on another table by cutting four fields then saving then pasting them back into the table and saving again. I tried importing the entire DB into a new file, this I still get the error message "Property Value is too large" ... View 1 Replies View Related Error 3309 Apr 22, 2005 I am putting a validation rule in my table that is In (0,1,2,3,888) or is null,