Properties size - 3309 mystery.

[EugeneG]

Hello, All.
OK, there is an Access 2000 DB.
One of the tables is huge (200+ fields).
I've got to maintain the database; lots of forms, DAO code need changes, as well some modifications to that table.

Any attempts to save the changes to the table result in
3309 - Property value too large.
Columns can still be deleted/added, of course; and changes stay, despite the exceeding properties size error, but this is not enough.
Setting properties for anything is never saved because of the error.

Too many forms and too much code is bound to that structure and no time at all to normalize the table and change everything else.

Worse, the original programmer is nowhere to be found.

But how the HELL was that monster table originally saved with all the properties and even lengthy column descriptions in the first place???? And it works perfectly with all the forms/code.

Please help me understand!

 

[TomCologne]

Start here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;323657&Product=acc2000

TomCologne

 

[MichaelRed]

While not as sagacious as TomCologne, You might want to consider that regardlessof the time available, you WILL end up restructuing (at least) the table in question and it's immediate consummer objects.

Philosphy (WHY or even HOW) it got there is just an intrersting 'water cooler' discussion, best saved and savored like revenge, served cold.

The immediate issue is, or should be, the inevitable discussion with the "boss". If 'he' is knowledgable re relational db, hte discussion should be relatively easy, otherwise, I would prepare with some documentation re the aims golals and limitations of the programming environment, and (perhaps) at least a brief discussion of the rationale for these.




MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[EugeneG]

Michael Red,
you are certainly correct.
All the new related fields will go in a separate tables.
And the huge table will be restructured eventually.
But I thought if there is a way to save these things it's nice to know of it, having to maintain and deliver functionality fast.
For now i'll achieve objectives through code and new tables.
And let that monument stand.
For now.