Thanks again. I agree with you that it exists somewhere :) . I am betting that it creates an XML file or something like that. If I figure it out, I will come back and post the solution.

Thanks to you both. I guess that makes our decision easier. I downloaded an ISO from our MSDN Subscriber website. The name of the ISO was mu_visual_studio_2015_update_3_x86_x64_dvd_8923065.iso I haven't attempted to install it yet. But the name of the file makes it look like you could install as x86 or x64. But maybe what it really means is that it will install to an x86 or x64 machine.

Thank you for your reply. All of our shared datasets point to stored procedures. I think I just figured out a solution. I have done this before. I don't know why I didn't think of it before. I am going to have my program download the shared dataset as an .rds file and then look at the xml tag CommandText in the rds file.

If number of controls are more you can use TabControl to group related sections.

You're welcome!

No need for apologies... Different experiences. With ERP systems, I configured the query screens based on the "questions" users wanted to ask; that always involved some combination of: Company; Department; Cost Centre; Client #; Invoice #; Work order $; Year; Month; Day; etc. Some required fields; some optional; default values off the accounting cycle. Write once (all variations of the same but limited to "codes" in their HR profile). Every new table / "entity" is automatically secured based on "need to know". No "bad" queries in the "operational" world; for the "informational" needs (different ASAP), there is the data warehouse. Two worlds.