Re: Magritte Post

Interesting. From my own experience, I've seen this problem first hand. A couple years back, I was thinking of the same basic principal that Magritte solves. My family owns a small business, and have a software program tracking customers and other related data. Certain data however, would have no applicable field. So it would instead be placed in a "Customer Notes" text field. Several issues came from this. The obvious is it was essentially impossible to search and sort. The data was extremely inconsistent. "Customer has pets" is different than "Customer has a dog", etc. Even remembering to note if a customer has pets or not is a challenge, since the field wasn't required. It also brings up training issues with new employees. And this is just a small business, the problems would be amplified with larger companies. On top of all that, it would be nice if you could market to specific "customers with pets" as an example. So you are losing a potential revenue stream here. And that is just one little field. I remember thinking at the time, it would be nice if you could create fields on the fly maybe using a oodb. Giving a place for the data. The idea kinda got stored somewhere. Probably never to be brought up again. But when I learned of Magritte it immediately sparked a light bulb in my brain. -- Jason Yates jaywhy(a)gmail.com