Happy new year all, I'm sure there is a technical term for what we're trying to approach, maybe someone can enlighten me.
In our database, we will be using A4D for data collection, year over year, with varying amounts of data and fields. For each respondent, they might collect 100 fields of varying types of data that gets pushed into specific places in the database. We want to be able to store a hash table of fieldnames, database fields they relate to in displayed data, and the data itself. And we want this to be generic so we do not have to continue creating field names, new tables and the data fields they reference. So, a database within a database? What we would like is a set of classes or routines that interoperate with table(s) to allow storing field names and data generically. Essentially building a storage and retrieval system for an indeterminate amount of data. Make sense? Collections are good. ObjectTools is good. But I need to be able to operate on the data as if it was separate tables and field names, storing generic field references with coercible data without getting bogged down with specific routines for accessing that data. Any references on how to build something like this, what it is called or better yet, an open source model upon which to build/migrate to 4D, would be spectacular. Oh, and I need it by tomorrow. :) We are building it into a custom system we are developing. Thanks, and again, have a happy new year everyone! Michael Check _______________________________________________ Active4D-dev mailing list [email protected] http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
