Error refreshing titles: Access Violation
 

I got this error consistently every time I select some text in the editor, hit F2, or go item-->rename to-->selected text. See attached.

Any ideas?

That works ok here. Does the problem occur in a new database? Please ZIP and send or post:
1) The info from Help | About | Install Info
2) A .urd file with an item that demonstrates the problem (indicate what text was selected when renaming).

Thanks.

When I bounced UR, it worked fine. I did not get so far today. I would like to kindly ask if you can just share with us how is UR doing this rename process? Is itusing clipboard to capture selected text?

It does not use the clipboard, but retrieves the selected text from the detail pane window/control using the relevant API calls.

Kinook,
this has returned again. This is what I was doing when it returned ...

- I was copying multiple items 5 and moving them around.
- When I was done, I created a new folder.
- I, then, gave it a new name or hit enter. I got the error.
- If I leave the new folder with its default name of 'new folder'. I do not get the error.

- It happens on all newly added items.
- closing the DB (not UR) clears it.

Do these errors affect data integrity at all? In otherwords, is it better to bounce UR when these errors happen just to be safe?

I wasn't able to reproduce this behavior. Can you provide more detailed steps (including information on open tabs) and/or a sample database?

That error should not affect data integrity (and it's possible that the rename worked and refreshing manually [Tree | Refresh All or Shift+F5] will update with the changes).

Thanks.

I can not myself reproduce it. In 2 instances, even copying the trouble items to a new DB does not do it. It is very hard if not impossible to catch these in such a reproducible manner.

On the other hand, oftenly, these DB has private or corporate data that can not be shared. This is the case for myself and I did see some other users indicating so as well.

I do not know how much logging is UR doing? But it does not look like it does a lot if any. But, may be you can consider implementing such a feature so we can overcome the limitations of the current approach (i.e. send .urd file and have to reproduce an otherwise hard to catch events).

Just a thought. I will keep an eye on these nasty AV pests.

Ok, kinook...
I got hit hard with this nasty error today. After working for 3 hours with a DB, it started appearing and I just could not get rid of it. Every time I created a new info item, it just showed up. One thing I did to resolve it without having to bounce the DB, is close all open tabs. Once I did, it cleared. I was able to add with no issues.

Does this make sense at all?

We've made some changes for the next release that will hopefully prevent this problem.

When will the next release be released? Thank you.