Sure thing Debbie. Those of us who write SQL queries often have to give our query/report processes over to others who don’t necessarily know how to code SQL. With that being said, the use of variable prompts can be important for them to run queries, but change criteria on them without having to actually update each SQL file for them. A good scenario is say about 5 different queries that need to run and export reports for a process. Instead of them going to each of them individually, even using prompts, but running and exporting them in a specific format, they can use the automation task which will have the queries pre-stored, and the export specifications already set. My idea in a specific case is all the reports go to tables in an access database for further reconciliation against large data sets. With that being said, this prompt in the automation will allow them to accomplish many reports and automatic exports while only hitting the run button of the automation and entering the variable prompts and the reports generate as needed automatically, allowing in increase efficiency, plus allowing users who have little to no experience to run the same things we run on a day to day basis or for backup purposes. I saw another post from another user, who I believe was trying to accomplish the same thing with his company with other employees with less query knowledge in mind.
Lastly, I will say, that the workaround at this point is to have the variable set action at the beginning of the automation task and basically instruct the users to input each variable on that variable action before running the automation. This is fairly basic and will suffice for now, but if prompted, it could surely make it just a tad bit easier, especially for users with no toad data point experience at all.
Please let me know if you have other questions.