Hello, I appreciate the suggestion, but I think that would give up all the usefullness of the framework for those fields. Also, for reporting purposes the data really needs to be in standard database tables, columns and rows. I think I'm going to hack around in the code a bit and see if I can patch it to get the behavior I need since this doesn't seem to be a common problem.
Thanks, -Chirs --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
