>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-25 16:02:51 Id:232
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.
-------------------
**_hardin4019:_**
**_Gents, I find this one strange. If I build a list with a query and have data in it, I can't click on the list and use CTRL+C to copy the data and paste it into Excel or a word document. This option works if you do the same thing to "Display Points" list that show you what points are associated with an RTU, and other system generated lists. Any ideas on a way to make this same functinoality work on a custom list based on a query?_**
----------------
sbeadle:
Hi Shawn,
Is your custom query on a mimic or a standalone window?
All standalone list query windows can be copied from the Ribbon menu.
Steve
-----------------------
**_hardin4019:_**
**_Steve, the lists I am referring to would be embedded into a mimic. Any work arounds other than say making these stand alone lists?_**
------------------
sbeadle:
I have seen two workarounds.
One (easiest) is to have a button adjacent to the list on the mimic. This runs a short script to open the list as an inset. The script copies the list sql (List1.SQL property) to create the inset link.
The second is to have a button which runs a script and executes the query, copying it to the PCs paste buffer. Generally this needs the user to click an 'allow' dialog which Windows demands.
---------------
**_hardin4019:_**
**_I'm not real good with ST or scripting, but I am learning as I go. What are the basic commands I would need for the script in option 2? This whole thing is more for the system admins. Operators don't have access to anywhere to even paste data. Admins would be using it to compare point values, addresses, complex query results, etc._**
------------------------
geoffpatton:
There are also two ways to get a SQL query results into a file.
1 You can print a embedded list to a PDF printer.
You can even select and copy the results from it. That adds a extra step vs Steve's second suggestion.
It is what I tell customers to do on an existing system where they suddenly need to put ... in Excel to analyze it yesterday.
2 Where someone wants something periodically I use a "SQL Export" object and have it create a new csv file in a folder on the MAIN server's hard drive or better a network drive.
I mostly mention these in case someone else comes across this thread and maybe these will work better for their needs.
----------------
**_hardin4019:_**
**_Understood. I did do a SQL Export yesterday to compare 2 special lists of RTUs to see if a change to the query had positive or negative effects._**
