chozma
Member
Hi all,
Bit of an interesting one this, hope you might be able to shed some light on what could be going wrong...
I have a list called Animals which is the lynch pin of my database/website. It joins with three other tables (Mobs, Events and Treatments), has all sorts of pre-filters on it and 11 elements of its own.
Last week I added a new element (number 12) to the Animals list. It is a dbjoin element which links to another table called Breeds and I have 'Add option in front end' set to yes.
Anyway, now when you save the Animal form it is deleting some of the data from a record in the Mob list, which is joined to the Animals list. The record is still there, its just that some of the elements are being changed to 0 or empty. It didn't used to do this before the addition of the new dbjoin element.
I did a couple of other small changes on the same day as adding this new element but this mostly involved adding 'back' buttons to my forms. If I disable the dbjoin element it hasn't solved the problem. If I get rid of the back buttons, same thing, it isn't fixing the problem. It is still misbehaving and wiping data.
Do you have any suggestions as to why this might be happening - might this be something you have come across before? Anything I could try to debug it?
Thanks,
Hannah
Bit of an interesting one this, hope you might be able to shed some light on what could be going wrong...
I have a list called Animals which is the lynch pin of my database/website. It joins with three other tables (Mobs, Events and Treatments), has all sorts of pre-filters on it and 11 elements of its own.
Last week I added a new element (number 12) to the Animals list. It is a dbjoin element which links to another table called Breeds and I have 'Add option in front end' set to yes.
Anyway, now when you save the Animal form it is deleting some of the data from a record in the Mob list, which is joined to the Animals list. The record is still there, its just that some of the elements are being changed to 0 or empty. It didn't used to do this before the addition of the new dbjoin element.
I did a couple of other small changes on the same day as adding this new element but this mostly involved adding 'back' buttons to my forms. If I disable the dbjoin element it hasn't solved the problem. If I get rid of the back buttons, same thing, it isn't fixing the problem. It is still misbehaving and wiping data.
Do you have any suggestions as to why this might be happening - might this be something you have come across before? Anything I could try to debug it?
Thanks,
Hannah