TableTime
asked on
Property Value too Large
I cannot open a table in either datasheet or design view. What specific property does this error refer to. And how can I fix it if I cannot get to the design view?
Property value is too large. (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.
Property value is too large. (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.
Have you tried to run the repair utility?
ASKER
Yes, it does not help.
How big is this db? Have you tried to import the table into another db?
ASKER
I exported the table into a new/blank database and it opens fine and I can view design as well without any changes. The size is 12.5 MB for the whole db. It is only one table in the db that does not work.
If you are using the security wizard make sure you have the rights to open the table in that database. If you do and it still will not open....
Remove all relationships from the table in the main db. Export to new temp DB and save.
Delete the table from your main DB. Run compact/repair. Import the table from the temporary DB. Try opening it.
I have had this happen in the past and that was how I worked around it. Still not sure what caused it.
Wallew
Remove all relationships from the table in the main db. Export to new temp DB and save.
Delete the table from your main DB. Run compact/repair. Import the table from the temporary DB. Try opening it.
I have had this happen in the past and that was how I worked around it. Still not sure what caused it.
Wallew
ASKER
I also did this because this has happend to another database I am working on. But with this one it did not work. We recently upgraded to Office XP, I do not know if this has something to do with it. Did you upgrade to Office XP?
No. This actually happened with a ACC97 database years ago. I am assuming something got corrupt in the MDB structure that prevented me from opening the table. Using the method I described before did resolve it though.
We are trying to stay away from XP until at least SP3 (or Subscription Advantage upgrade 3 or whatever MS calls it now.) Not to mention I really don't care for their new licensing structure. Hoping that Lindow's will give us a better workstation OS. http://www.lindows.com
Something has to change! Sorry. Just had to ge that out.
Wallew
We are trying to stay away from XP until at least SP3 (or Subscription Advantage upgrade 3 or whatever MS calls it now.) Not to mention I really don't care for their new licensing structure. Hoping that Lindow's will give us a better workstation OS. http://www.lindows.com
Something has to change! Sorry. Just had to ge that out.
Wallew
I've seen this happen before and there is no fix for the current MDB container. The problem is that the MDB container contains invalid information in the area where a property value is stored for either the table or one of the fields.
When Access tries to open it, it fails. What's really suprising though is that you can export it! Generally, this is not fixable and a backup is your only recourse.
But in any case, create a fresh MDB file and import eveything into it. Do not continue to use the old container.
Jim.
When Access tries to open it, it fails. What's really suprising though is that you can export it! Generally, this is not fixable and a backup is your only recourse.
But in any case, create a fresh MDB file and import eveything into it. Do not continue to use the old container.
Jim.
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in Community Support that this question is:
- PAQ'd and pts removed
Please leave any comments here within the
next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER !
Nic;o)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.