YAC (Yet Another Crash): deleting an item property

[cnewtonne]

Dear Kinook,
After putting up a ferocious fight with UR, I eventually won and was able to tame it and have it behave with some discipline. This is what it did ...
- started spitting out these errors about FK issues(see attached).
- The tree disappeared and refused to close (with above error). I had to kill it.
- Once bounced, it worked fine.

This is what I did...
1) renamed an attribute from 'archive' to 'ToPurge'
2) modified form to display new attribute.
3) existing items using this form continued to display 'archive' instead of 'ToPurge'.
4) I eventually delete the attribute 'ToPurge'.
5) created a new attribute same name
5) started getting this mess.
6) after killing UR and starting it again: form displays the new attribute 'ToPurge'


Can you please take a look and repair this issue please.

[kinook]

#2/#3 should be automatic after renaming an attribute. You refer to display "new" attribute. Did you rename an existing or create a new attribute?

#4 should also delete any item attributes for that attribute

What did you do in UR when #5b occurred? Creating an attribute triggered it?

Please ZIP and send or post:
1) The info from Help | About | Install Info
2) A .urd file that demonstrates the problem

Thanks.

[cnewtonne]

Thank you.
I was able to reproduce the issue in a brand new DB. Please follow these steps ...

1) create a new DB
2) create new attribute (test-attr)
3) create a new form and place above attribute in it plus some other existing one.
4) modify task template to use new form.
5) create a new task to see new form.
6) rename attribute in step 2 to something else (test-attr-01).
7) you should see form update with newly modified attribute name.
8) now, delete the newly modified attribute test-attr-01
9) switch to another item.
10) you should get the error message I posed earlier about FK violation.

Let me know.

[kinook]

Thanks. I couldn't reproduce any errors when renaming an attribute, but I was able to reproduce that error by:
1) Creating an attribute
2) Assigning it to a form
3) Creating an item that used the form
4) Populating the attribute on the form
5) While still at the item, deleting the attribute
6) Switching away from the item or closing the database

After the error was displayed, I could still exit UR (File | Exit) normally and the problem went away on restarting UR. This will be fixed in the next relesae. For now, you can avoid this problem by a) not deleting an attribute when a form is showing that attribute (select a non-form item first) or b) removing the attribute from the form before deleting the attribute.

[cnewtonne]

Marvelous...
It feels rewarding to catch these instabilities and bring it to your attention for a repair.

UR is a great product and I'm glad to contribute to its advancement.