Hi Susan,

I'm happy to see you experimenting with GridView - it's the only way to really learn about the product. Feel free to ask questions about the location of specific data in the Technical Support Forum. It will be faster than "poking around" (although that is a learning experience in itself).

In answer to your specific questions:

1)You purhcase GridView Server in addition to GridView. With GridView Server, the filters are run on your server, rather than sending the whole file up to the workstation to process the selection. While it won't be quite as fast as processing the query on a local set of the data, you can expect performance to be 4-10 times faster than moving the entire dataset over the network. If the large inquiries are only being run at the end of a month, you might consider moving a copy of your data onto your local workstation and running the Views against the copy (not that I want to discourage you from purchasing another module!).

BTW - you can often improve the performance of a View by restructuring it to take advantage of some of the indexes maintained by Adagio. However, searching for transactions within a specific date range usually requires scanning the entire file.

2) If you save Views in a common subdirectory, then others will be able to find and run them. Also, you can attach Views to the Inquiries menu choice of an Adagio application by saving the workspace in the \SOFTRAK\xxxxx\VIEWS subdirectory (where xxxx is your program subdirectory. An option under File | User controls whether a user is allowed to change the columns in a View. You can also place a shortcut on a Users dektop that will launch GridView and open a workspace directly using the /wworkspacename.GVS command line parameter. Users can then just click on the shortcut to open the View.

3) You don't need to add GridView to the list - there's nothing in a View definition that DataCare can check.