Sandy R Posted July 12, 2004 Posted July 12, 2004 I need to deselect everything on a window. I need this because I'm popping up a new window with some editing controls and I get an error that the record can't be modified because it is being modified in another window (the original one). However if by hand I click on an empty area of the orignal window..and then pop up the new one...I can edit the fields. So I need to programmatically deselect everything. Help! ..thanks...Sandy
Fenton Posted July 12, 2004 Posted July 12, 2004 Commit Record. Very important step, especially in 7. Whenever you have "opened" a record(s) in a script, whenever you've set or edited a field, it's a good idea to put this step afterwards (only once; unless you open it again). As you've discovered, leaving a record open can block you if you're trying to work in multiple windows. It does the same to multiple users on a network.
Sandy R Posted July 12, 2004 Author Posted July 12, 2004 Thanks!! Works like a champ....gotta love this forum! Sandy
Jarvis Posted July 13, 2004 Posted July 13, 2004 LaRetta & Fenton, Thanks for that tip about Committing the record. I have scripts that include several GO TO LAYOUT commands. Periodically I would encounter the same roadblock Sandy described. Did I read you to say it would be useful to include the COMMIT RECORDS at the end of each script that ends up opening a record? Jarvis
LaRetta Posted July 13, 2004 Posted July 13, 2004 Hi Jarvis, I still stumble on this one. I get it mostly when I open a new window to the same data set. If when clicking a button, the script won't activate, it usually means I didn't exit a field (de-select). I don't think a simple layout switch is a problem if it stays in the same window. I find myself adding this script step more and more, but I have no specific list of when it is appropriate. It would be nice to accumulate one.
micshrp Posted March 9, 2005 Posted March 9, 2005 I've had a similar problem and now I've inserted the Commit Record/Request step. However, I'm unsure if this has remedied the problem yet or not. The error where the record can't be modified because it is being modified in another window did not always occur. It seemed to happen at random and I'm unsure why. Hopefully the commit step will take care of the problem. Otherwise I'm not sure of another work around. Is anyone able to explain the error of not being able to modify a record because it is being modified in another window, i.e., why does it occur at random?
micshrp Posted March 9, 2005 Posted March 9, 2005 I've had a similar problem and now I've inserted the Commit Record/Request step. However, I'm unsure if this has remedied the problem yet or not. The error where the record can't be modified because it is being modified in another window did not always occur. It seemed to happen at random and I'm unsure why. Hopefully the commit step will take care of the problem. Otherwise I'm not sure of another work around. Is anyone able to explain the error of not being able to modify a record because it is being modified in another window, i.e., why does it occur at random?
micshrp Posted March 9, 2005 Posted March 9, 2005 I've had a similar problem and now I've inserted the Commit Record/Request step. However, I'm unsure if this has remedied the problem yet or not. The error where the record can't be modified because it is being modified in another window did not always occur. It seemed to happen at random and I'm unsure why. Hopefully the commit step will take care of the problem. Otherwise I'm not sure of another work around. Is anyone able to explain the error of not being able to modify a record because it is being modified in another window, i.e., why does it occur at random?
Recommended Posts
This topic is 7566 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now