I have a set for which I need to make changes to field rules. When I open the set in design mode to edit the field rules I get a message to the effect:
"The Table/Set is being used by another session and cannot be opened in exclsuive mode. Field rules can be viewed but no changes can be saved."
If the set is opened in design mode to edit the set structure no such exclusive access message is generated and I can edit the structure with no problems.
Well the set/tables are in fact not in use by another session. Just to make sure I unload and reload Alpha, but the message still appears. Then I do a complete reboot of the computer just to ensure nothing is still being held in memory or being run as a process that might cause this. No success. So then I duplicate the set to a new set and the message still appears for the new (duplicate) set. Huh? Is Alpha writing access mode flags into the actual set definititon? I would certainly hope not. How can I clear this problem, or am I screwed and will need to completely recreate the set from scratch?
As a general observation, I have encountered numerous instances with V8 seeming to get randomly confused and issuing similar exclusive access messages. In all cases, except the the present one, closing either the application and/or Alpha itself and restarting has cleared the problem. But, getting random exclusive access locks isn't good and shouldn't be happening. It's as if Alpha isn't consistently releasing locks on sets or tables when it should. Anyone else experience this behavior?
"The Table/Set is being used by another session and cannot be opened in exclsuive mode. Field rules can be viewed but no changes can be saved."
If the set is opened in design mode to edit the set structure no such exclusive access message is generated and I can edit the structure with no problems.
Well the set/tables are in fact not in use by another session. Just to make sure I unload and reload Alpha, but the message still appears. Then I do a complete reboot of the computer just to ensure nothing is still being held in memory or being run as a process that might cause this. No success. So then I duplicate the set to a new set and the message still appears for the new (duplicate) set. Huh? Is Alpha writing access mode flags into the actual set definititon? I would certainly hope not. How can I clear this problem, or am I screwed and will need to completely recreate the set from scratch?
As a general observation, I have encountered numerous instances with V8 seeming to get randomly confused and issuing similar exclusive access messages. In all cases, except the the present one, closing either the application and/or Alpha itself and restarting has cleared the problem. But, getting random exclusive access locks isn't good and shouldn't be happening. It's as if Alpha isn't consistently releasing locks on sets or tables when it should. Anyone else experience this behavior?
Comment