LaRetta Posted January 18, 2018 Share Posted January 18, 2018 Just now, OlgerDiekstra said: I probably should have mentioned that the ExecuteSQL I used was in a script. Considering OneStop's request, an unstored calculation which needs to compare every record in the same table using DISTINCT, particularly if any record is open, would be a resource nightmare as I suspect he discovered. But why not simply create a script which uses that same single ExecuteSQL() step after making sure the record isn't open? Via script is the only way I ever use *ExecuteSQL(). Ah well, I shouldn't have stepped in since I didn't take the time to read the entire discussionl. Thank you for clarifying, Olger! * and yes, there are always exceptions such as a smaller or single-record tables. Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 2283 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