A statement over a table of a cloud platform returns forty columns where three are being looked at. The [[Invantive Query Tool/Results|Results]] grid is arranged rather than the statement rewritten, and the arrangement is kept for the next time. ## Moving and Sizing A column is moved by dragging its heading sideways, and sized by dragging the edge of the heading. Double-clicking that edge sizes the column to its widest value. ## Pinning The arrow on a column heading pins the column, which keeps it in view while the grid is scrolled sideways. On a wide answer this is what keeps the key column beside whatever is being read. ## Hiding What Is Empty "Hide empty columns" on the toolbar leaves out the columns which hold no value in any row of the answer. On a table with many optional columns it shortens the grid considerably, and it says something as well: a column which is empty over the whole answer is one the platform does not fill for these rows. ## Keeping the Arrangement "Display Layout" saves the arrangement and applies one saved earlier: the widths, the order, the pinning and the grouping. A saved layout belongs to the shape of the answer rather than to the document - it is held in a file of its own in `%USERPROFILE%\Invantive\Layout`, named after the columns the statement returns, and is offered again for every statement returning those same columns. Two different statements which happen to select the same columns therefore share a layout, which is usually what is wanted. ## What Is Not the Grid's Business Which columns are fetched at all is decided by the statement. Selecting the three columns being read instead of `select *` saves the platform the work of the other thirty-seven and the connection the traffic; the grid can only hide what has already arrived. On a platform which is charged per call or per row that difference is money, and the [[Invantive Query Tool/Connection Monitor|Connection Monitor]] shows it as bytes received.