Malcolm Tredinnick wrote: > We may need a bit more information there. It sounds like (from the title > of this email, which isn't mentioned anywhere else here) like one of the > fields you are expecting to be non-null is empty and so the related > instance doesn't exist and you can't query against it. However, it's > very hard to tell.
Malcom, thanks for the help! I suspect that paragraph above is where the problem lies. I'll vaugly remember changing some of the blank/null options a week or so back --around the time my troubles started. I'll whittle it down and report back. Regards, Johnny --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
