I see the grid as a tabulated list of data that does not speak all about itself - usually requires a header (a form with the parent data of these records) and a summary.
In the listview I see as a list of more complete objects (not necessarily with more information - maybe just the opposite), this list may have different views depending on the information about these objects that you want to have highlighted at that moment. / p>
Example: A list of files in a Windows folder
Purpose: An overview of the folder
If your goal is to get an idea of the amount of files and space occupied by these files, you would probably want to list them on a grid, seeing in the header the path of the folder and in the table of contents the number of files and the space total busy.
The grid with the list of files in this case has a secondary function to give an overview of the files that are there.
Purpose: An analysis of the files that are in the
Now, your goal can also be the files themselves.
You may be wanting to understand things like: Is this folder more for work or college papers? What types of files do I have here? Are the images that are private here?
In this case you will probably want to list the files in a listview, with large icons that reveal the type and eventually a bit about the content as well as the filename, and eventually you will want more details about a particular file and will click on it to see the size and creation date without having to navigate to another form.
In the first case the focus is on the whole, and the list is only a part of this whole; then we use grid.
In the second case the focus is on the item, and the list allows you to switch between different views and reveals a lot about each item not only in tabular form but also with the information arranged in the item itself; then we use listview.