local SharedObject size limitations

[adamjbrown]

I am developing a CD-Rom application which uses, what is essentially, a series of complex objects stored in a local SharedObject as a database. My question is has anyone ever really tested the size limitations of the local SharedObject? I realize that the user can set them to unlimited but I would like to know if anyone has pushed that limitation. Im trying to get some piece of mind. Thanks.

[corroded]

i think if you try to push a limitation, flash will ask the user again if he or she wants to give more space for the SOs.

[adamjbrown]

If you try and push over 100k they user is prompted. They can set the amount of size of the sharedObject to unlimted then. Im just wondering if anyone has really pushed the size limit of the sharedObject itself. Im building a product that has a local cd-rom version and network version. The network version uses SQL to store data. The local version has various tech limitations that are causing me to re-create that SQL database in a sharedObject. Sounds crazy, I know. I just want to make sure its going to be stable when I ship this thing and people start adding data to the object.