Russ, Thanks fo the reply!
> The only thought I have is that you appear to be using a pre-existing > table to manage the m2m relationship, rather than the default produced > Django table. This shouldn't pose a problem, but it does lead me to > wonder if there is some other process that could be using that table. Hmm, not really, maybe I gave this impression when I "simplified" the name of my models (A and B, etc.), but it's really all Django-created and managed stuff. > Other than that - this has all the hallmarks of a user error. Are you > in a position to 'sit on your client's shoulder' until the problem > reproduces itself? Yes, that's what I'm trying to do - of course, being a 'randomic' error it follows Murphy's laws, and I'm never there when the 'problem' happens, whatever it is. I'll keep trying, though! Thanks again, Rubens --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
