
Originally Posted by
Cheryl Lemire
I can only guess that dewayne is talking about queries that are created on the fly by users with query by form, key, index, etc. This is the only place that I am aware of where there are limitations. With this 'guess'
dewayne,
If your users are creating complex queries that need to be used on a regular basis, may I suggest that you create a query operation for them and allow them to run that script whenever they need it via a specific query button. This way you do not have to worry about the query being deleted.
If my 'guess' is off the wall, you need to be much more specific with the problems. Where are you users in the runtime when they are creating the queries in the first place? Exactly what steps are they taking to create this query? Provide us with a zipped up sample of the db and give us exact steps to duplicate the query creation. Then tell us 'how' you know their query has been deleted.
The 'devil is in the details'. I do not remember how many threads I have read that it .... but if you do not give us enough samples and step by step instructions to duplicate the problem .... we are all only guessing at what the actual problem is .... hence, our solutions are only guesses as well. It saves everybody a lot of time when details and samples are provided.
Bookmarks