I have a client who has an application he wants me to build. I'm going to use Zope. The question is whether I should use the built-in object database or an SQL database. I _vastlly_ prefer the former; I tend to think in objects. Each client object in the system has potentially 350 separate properties. These are entered, reported, and managed through a series of about 12 forms. Some of the forms can be used by the client to create multiple entries of the same type. I can see exactly how to architect this. But my question -- which I can't seem to find an answer to -- is whether there's a practical limit (or a built-in limit) on the number of properties an object can/should have in the Zope built-in object database. (I'm using MetaPublisher to create the interface and the objects if that makes any difference, though I'd be OK with not using it if it turned out that it had a limit.) -- Hire a world-class ghostwriter to create your entire information product line! Dan Shafer, author of 57 books (and counting) - Ghostwriting Unlimited, Inc. dan@gui.com - 831-643-0590 (V) - 831-401-2531 (F) http://www.gui.com