SQL Server Data Editing Made Easy
release notes
  • The text editor now shows the length of the text.
  • The row inspector panel can now be hidden by unchecking "Show Row Inspector" in the Preferences dialog (File | Preferences | Worksheet).
  • Added the new Export Field to Files assistant under the Assistants menu. For tables containing text or binary fields, as well as a field designating a filename, you can export each row's data contents to an independent disk file.
  • The user may now define custom colors for various grid cell characteristics (readonly, alternate row, etc) from the Preferences dialog (File | Preferences | Styles).
  • When connecting to a database server using a port number, port values up to 65535 are now allowed.
  • In the database browser, the System Tables and System Views categories are now hidden by default. They can be restored by selecting them from the Database menu.
  • Fixed the text editor Word Wrap button which was not keeping its state correctly.
  • Changed the shortcut key for the Assistants menu to avoid a conflict with the shortcut key for the Data menu.
  • Fixed an issue when inserting rows into a table with SQL Server 2005 and the user is not the table owner. If a field had a default value assigned and was declared NOT NULL, then OmniView would show an error "Field XXX must have a value" rather than let the default value apply. This has been corrected.
  • Fixed the Best Fit (All Columns) feature which was not optimizing the display width of very long character fields. The maximum display width of character fields is controlled from the Preferences dialog (File | Preferences | Datagrid | Best Fit Text Width).
  • Fixed the Best Fit feature to account for the width of <null> values properly.
  • Fixed script worksheets which were displaying empty.
  • Fixed the error "MouseTrackingTimerList.Count <> 0" in the MDAC upgrade warning dialog.
  • Fixed varbinary(max) fields (MSSQL 2005) so they are no longer treated as text fields.
  • Fixed the worksheet tab tooltip which was always showing the active tab tip even when hovering over an inactive tab.
  • Fixed the text editor to synchronize with the current data when a worksheet is refreshed.
  • Fixed the filter designer popup editors which should have no window caption.
  • On Windows Vista, an incorrect MDAC upgrade error message was being shown.
  • Fixed an issue in the filter designer where the expression operator menu would not open if the referenced column name was qualified.
  • Fixed private views to save the joined table portion of a filter.
  • In the row inspector, squeezing columns to the minimum width possible obscured field names and left them impossible to unobscure.
  • For Windows earlier than XP, the gdiplus.dll is now installed in the application folder. If the operating system didn't have GDIPlus already, then starting OmniView would show the error "OmniView.exe has generated errors and will be closed by Windows. You will need to restart the program."
  • Fixed several problems with joined tables in filters with tables not owned by dbo.
  • Text, ntext, and image columns can no longer be selected for sorting.
  • The currently connected server and database is now shown in the status bar when no worksheets are open. When one or more worksheets are open, it is the server and database for the active worksheet.
  • On SQL Server 2005 with a database compatibility less than 90, object owners are now correctly shown when the owner is a schema.
  • Changing the "Allow Editable Views" preference now changes the state of the active worksheet right away (if it is a view) rather than waiting for a refresh.
  • When saving a new private view with the same name as another private view on the same table, the private view toolbar dropdown now changes to reflect the new private view.
  • Opening a stored procedure worksheet no longer tries to execute the stored procedure right away if there are parameters on the stored procedure. This was a problem introduced in a recent release.
  • When executing a stored procedure which returns an empty result set, an empty data grid is now shown (rather than no data grid at all).
  • Multirow Update Assistant no longer produces an "invalid typecast" error if executed on an updateable view.
  • Loading an existing private view no longer causes a runaway error condition which terminates the application. This was a problem introduced in a recent release which occurred under certain circumstances.
  • Changed table properties display for foreign keys.
  • Changed table properties display so that the default sort order for columns is position rather than name.
  • Added a worksheet navigator control in the upper right of the worksheet display.
  • Changed the worksheet tab display to resemble the tabs in Microsoft OneNote.
  • Added a "Close All Other Worksheets" option to close all worksheets except the active worksheet.
  • The Multirow Update feature has been removed from the Data Tools panel and placed under the new Assistants menu.
  • Fixed a "List index out of bounds" error when the Tech Support Wizard was closed.
  • Changed filter designer to show table owner names when the Show Owner option has been selected.
  • Fixed an error that would occur when selecting Open All Group Objects if one or more of the group members were not present in the current database.
  • Fixed the Show SQL button in the filter toolbar which previously did nothing.
  • Fixed error in the stored procedure worksheet when clicking the edit button for a binary parameter.
  • Fixed a "list index out of bounds" error occurring when the Tech Support Wizard was closed.
  • Fixed filter designer popup menus so that clearing an existing parameter values does not display incorrect HTML markup.
  • Fixed the filter designer so that the mouse hotspot region for a parameter is correctly aligned over the parameter instead of being offset to the left by several pixels.
  • Fixed the new item row in the data grid to hide/show as soon as the worksheet is locked/unlocked rather than waiting until the worksheet is refreshed
  • Fixed Multirow Update to be unavailable if the worksheet is locked.
  • Fixed a caption display problem in the Data Export Wizard.
  • Fixed the permissions display; was not showing permissions.
  • Fixed an error when opening a script worksheet; introduced in the last update.
  • Fixed Close Worksheet context menu option to be disabled when not clicking on a worksheet tab.
  • Fixed the table properties display; was not showing index attributes.
  • Fixed the View | Show SQL menu item which previously did nothing.
  • Resolved a number of issues which resulted in unnecessarily reloading the data in a worksheet.
  • Clicking the ellipsis button in an image cell when the Data Tools Panel is not showing resulted in a "cannot focus a disabled or invisible window" error.
  • A "List index out of bounds" error could occur upon startup if a private view was previously saved using version 2.1.
  • Data from views can now be edited just like data from tables. Bear in mind that not all views are updatable and an error may be displayed if you try to change data in a view that is not constructed to allow changes.
  • When switching from a private view using a filter to a private view which does not use a filter, the previous view's filter incorrectly remained in effect in the new view.
  • The server information popup incorrectly identified MSSQL 2000 Service Pack 4 as Service Pack 3.
  • Numerous changes made to support SQL Server 2005 including support for objects owned by schemas (not always database users) and XML datatype columns.
  • Query worksheets did not honor the option to turn off the data grid's alternate row color.
  • Database objects listed in "Groups" where not showing owner names when the "Show Owner" preference for object names is enabled.
  • When switching from a private view with sorted columns to a private view which does not have sorted columns, the data would be unsorted correctly but the sort indicators in the grid's column headers would still show the old view's sort settings.
  • Using "Filter By Selection" on a null value produced the error "Could not convert variant of type (Null) into type (String)"
  • When editing a value in a data cell, the context menu now includes a "set to null" item which sets the current cell's value to null.
  • The default order in which data columns are displayed (by name or by position) is now set under File | Preferences.
  • Grid cell editor for datetime fields supports time editing.
  • Filter By Selection on a bit field always filtered for value 1, even when the selected value was 0.
  • Bound defaults were handled incorrectly when attempting to insert a row.
  • After registering an expired trial from the startup screen, the application would terminate and require restarting.
  • Selecting "Properties" from the database browser context menu would result in the error "A component named ovfResultsStatusBar already exists".
  • After loading a private view, the "Order Columns By Name/Position" items could be set incorrectly.
  • In the row filter, if a join expression was started but not completed, applying/cancelling the filter would result in an access violation.
  • Can now select a system database.
  • Selecting "Order Columns by Name/Position" didn't do anything in a query worksheet.
  • Alt-X was not working to execute a freeform query or a stored procedure.
  • Clicking a column header to sort the results of a stored procedure just re-executed the stored procedure.
  • Switching from private view to default view left an empty grid column if the view had a frozen column.
  • Frozen columns were not retained as frozen in private views.
  • Added incremental search to the Select Database dialog.
  • Adjustments made to better accomodate screen resolutions at 120 DPI
  • When a data worksheet (table, query, or stored procedure) was re-executed, grid layout customizations (column positioning, column widths, etc) were not retained between executions.
  • Query and stored proc worksheets now default output columns to "by position" order.
  • Opening a worksheet for a stored procedure with no parameters now executes the stored procedure immediately rather than requiring the user to press F5 after opening the worksheet.
  • Text within readonly grid cells can now be selected, which is necessary for copying the text to the clipboard.
  • Functions to select or save a private view have been added to the main menu.
  • "Best Fit (All Columns)" has been added to the toolbar
  • "Restore Default Toolbars" has been added to the toolbar context menu. Selecting this will remove all toolbar customizations and revert the toolbar configuration to its shipping state.
  • Fixed an intermittent error "Control 'pagDataTools' has no parent window" when selecting the Text Editor tab in the Data Tools frame
  • Previous release broke ability to store toolbar customizations
  • Fixed problem when exporting a worksheet dataset to a disk file, and selecting an existing filename, a "file exists" warning dialog appearred twice; once when closing the file picker dialog and once when clicking the "next" button on the export wizard.
  • Once connected to a server with an active database, trying to connect to a different server and selecting a database with the same name as the currently active database would not work.
  • If the Binary Editor is selected and a binary/varbinary field is focused, trying to load a new table in the same worksheet would produce an error "Field XXX not found" where XXX refers to the binary field from the previous table.
  • Fixed intermittent access violation when clicking on the Text editor tab in the Data Tools frame.
  • Fixed access violation when changing the font in the Text Editor.
  • Main window caption now removes the trial version warning after the software has been registered by selecting Help | Register from the menu.
  • Exporting a private view gave no warning if an existing file will be overwritten
  • Importing a private view did not validate that the file actually exists.
  • Loading a stored procedure worksheet and then double-clicking the same stored procedure name in the database browser, caused the stored procedure to execute, whether or not the user had supplied input parameters for the procedure.
  • When selecting <pin to worksheet> from the datagrid's toolbar field picker, the text "<pin to worksheet>" remained in the toolbar picker rather than the name of the currently selected column.
  • The private view toolbar can now be customized
  • If a filter is applied, then cancelled, then cleared, the filter status bar was not reset to <not filtered>.
  • Print and Print Preview function have been added for script worksheets.
  • In a query worksheet there is now an autocompete dropdown list for stored procedures after the keyword "exec" is typed.
  • A new option under File | Preferences has been added to control whether the Data Tools panel is shown by default when opening new worksheets.
  • In a stored procedure worksheet, pressing F5 did not execute the stored procedure.
  • Stored procedure worksheets could not properly parse stored procedure parameters when there were comments following one or more of the parameters. Also when a default value was assigned to an output parameter.
  • For query worksheets, the Print and Print Preview options were always disabled.
  • For query worksheets, the Export option was always disabled.
  • Switching between worksheets with private views could sometimes cause a "List index out of bounds" error.
  • Deleting a private view from the Database Browser would not remove it from the private view dropdown list in the worksheet's toolbar.
  • Database connections were not being recycled as worksheets were closed and new worksheets opened.
  • Loading a new table into a worksheet which already has a table with private views could produce an "Assertion failure" error.
  • Opening a private view via the navigator didn't repaint the worksheet caption with the view name.
  • Loading a second private view into a worksheet would not show the correct columns for the view. It would combine with the original private view in the worksheet and show only the columns that the two views had in common.
  • If a private view is selected in a worksheet, then a new worksheet of any type for any object is opened, then the new worksheet would show the previous worksheet's private view name in the worksheet tab caption.
  • Renaming a private view which is active in an inactive worksheet, did not change the worksheet caption.
  • When saving a new private view in a worksheet, the worksheet caption did not update with the new view name.
  • Renaming a private view to the same name as an existing view on the same table should not have been allowed.
  • A previous release broke the SQL editor for row filters. Filters using SQL expressions (not the SQL designer) were being ignored.
  • The Print and Print Preview options were incorrectly enabled when there were no open worksheets. Selecting either option resulted in an access violation.
  • The Export option was incorrectly enabled when there were no open worksheets.
  • When viewing a data worksheet, pressing the F5 key will refresh the data (identical to selecting "Refresh" from the toolbar or Data menu).
  • If a private view was selected for a table, and the worksheet was closed and a new table opened, then the private view name was erroneously carried over into the new table worksheet.
  • When saving a private view containing a row filter, if one or more of the filter conditions were disabled, they were saved as enabled in the private view and would appear as enabled the next time the private view was selected.
  • The SQL query editor was not syntax highlighting comments correctly.
  • In the Groups navigator of the Database Browser, right-clicking on a group name reveals a new menu item "Open All Group Objects". Selecting this opens each database object in the group in a new worksheet.
  • If an error occurred during query processing (e.g., a timeout), then the worksheet was in an unstable state. The grid status still showed "Querying..." and clicking on various grid controls resulted in error messages.
  • Once a table worksheet was switched to "Properties" the "Data" menu became disabled and there was no way to switch back to "Datagrid".
  • If a filter resulted in a query error, all the dataset and filter controls were disabled, so you couldn't correct the filter mistake and requery without closing and reopening the worksheet.
  • Disconnecting did not close open worksheets
  • With SQL Server 7.0, if a database contained any triggers, then trying to open that database would result in an error "Field 'islast' not found.".
  • When a private view was assign to "any object" it did not appear in the private view navigator.
  • When setting a query timeout preference under File | Preferences, the preferred timeout value was not being used.
  • Double-clicking an object in the database browser can either open the object in the current worksheet or in a new worksheet. Which action is taken can be set under File | Preferences.
  • The default Max Row Count for datasets returned in a worksheet can be customized by going to File | Preferences.
  • Worksheets now show the server/database they are connected to in the lower right of the status bar.
  • When using a filter, sometimes the Print and Export functions would become disabled.
  • Once any query worksheet was closed, opening any new query worksheets would result in an access violation for any key types in the new worksheet's SQL editor.
  • When registering a license, if an invalid key error occurs, then the user still gets the "You have been registered" dialog.
  • Worksheet toolbars are now user customizable.
  • When using a private view which contained a filter, the filter was not cleared when resetting the worksheet to "default view".
  • If there is an active worksheet, and the user changes databases in the database browser, then the context of the active worksheet changed to the new database. This may result in an error if the worksheet is refreshed because that table may not exist in the newly selected database. This has been corrected so the active worksheet keeps its original database context.
  • When loading a new table into an existing worksheet, the grid's status bar showing the rows returned by the query and the current filter status would disappear. The controls would not return until the application was resized or otherwise repainted, such as after being unobscured by another application.
  • In the Pro version, system databases (master, model, msdb, etc.) can now be viewed. They may be optionally shown or hidden in the Select Database dialog.
  • A main toolbar is now available at the top of the screen outside all worksheets. The interior toolbars on the script and stored procedure worksheets have been removed and their functions made available on the main toolbar. The main toolbar is also fully customizable.
  • There is a new main menu item called "Database". The Database Browser and Permissions menu items previously under "View" have been moved to "Database". In addition the Database submenu contains check items for each of the object categories in the Database Browser. Users can selectively show or hide the types of objects displayed in the Database Browser (i.e., hide the Private Views, but show all the others).
  • All of the disk file dialogs (for importing/exporting data and loading/saving files for the text or binary editors) now have a Favorite Folders feature. Users can keep a list of their most frequently used disk folders and select them to use in the Open or Save As file dialogs.
  • The stored procedure worksheet now uses the Data Tools panel in its result grid just like all the other worksheets.
  • When running under XP themes, two access violations occurred at startup. Then the program continued normally.
  • In a query worksheet, if a query is executed which does not produce a result set, and the user clicks on the Show Results Pane button, then an access violation was raised.
  • Many of the user interface controls were not being displayed correctly under XP themes.
  • In a query or stored procedure worksheet, before it has been executed and produced a result set, all of the items under the Format menu were enabled and many of them caused an assertion failure or access violation if selected.
  • The Private View Import Wizard had the wrong window caption.
  • In a query or stored procedure worksheet, before it has been executed and produced a result set, the Sort | Cancel All Columns menu items was enabled and caused an assertion failure when selected.
  • When running under XP themes, and access violation occurred in the Private View Import Wizard.
  • When running under XP themes, an access violation occurred in the Dataset Export Wizard.
  • When no worksheets are open and user right-clicks in the empty worksheet area, a disabled "Close All Worksheets" context menu appeared.
  • When creating a script for a stored procedure whose name or owner contained special characters (such as a blank), then the script would come out blank.
  • The Row Inspector context menu items were always disabled.
  • Under some circumstances, opening a table worksheet caused an error "Cannot focus a disabled or invisible window."
  • The Binary Editor was not showing data for binary/varbinary datatypes; only for image datatypes.
  • The Binary Editor edit functions (cut, copy, paste) were always disabled.
  • The Dataset Export Wizard now warns before overwriting an existing export file.
  • Exporting a dataset was only exporting buffered rows and not the entire dataset.
  • Loading a private view which had no filter caused an assertion failure.
  • Dragging a grid column into the Group By box caused an access violation.
  • Corrected a bug which prevented the Database Browser from displaying for a new installation.
  • Corrected cut/copy/paste functions in data grid cell editor and text editor
  • Error messages were not being displayed if an error occured when registering a license during application startup.
  • When a database was the "most recent" database from a previous OmniView session, and that database is dropped, the error "Recent database XXXX not found" was occurring at login. No error occurs now. The database is simply ignored.
  • In the filter designer, the template for bit datatypes was wrong. The "is not set" template used "<operand> <> 0" and it should be "<operand> = 0".
  • If the database browser is resized such that it is no longer visible, then there was no way to restore it. When this happened, the state of the DB browser was still "visible" even though the panel width was zero. The panel width always remained zero even if after toggling through View | Database Browser, or trying to move the splitter to the right to bring the DB browser back into view. The browser now behaves correctly when it is resized to zero width.
  • Corrected a number of glitches in parameter value type conversion routines for stored procedure parameters.
  • Professional Edition: Stored Procecedures - Use the parameter editor to set input parameters, execute the stored procedure and view output parameters or result dataset.
  • Professional Edition: System Tables and Views - Examine system table content using the same power data grid features available for user tables. Edit system tables if server permissions have been setup to do so.
  • Added private view Import/Export functions. Share private views with other users by copying or emailing private view definition files.
  • Redesigned graphical foreign key relationship display.
  • Added private view Copy function.
  • When creating a new group, the "Groups" header in the Database Browser now updates the group count.
  • "Properties" item added to context menu for tables. This opens a table worksheet with the Properties display showing instead of the Data Grid.
  • If using a filter in a table worksheet and then opening a new query worksheet, the filter status display from the previous worksheet no longer carries over into the new worksheet.
  • "conFilterStatus" is no longer displayed in a query worksheet.
  • In the filter SQL designer, expression operators for table fields of bit datatype are now limited to "is null", "is not null", "is set" and "is not set".
  • In the filter SQL designer, if a source table has been aliased, the alias can now be removed by clicking "no alias".
  • In the filter SQL designer, the second operand of an expression is now correctly bracketed if it contains an object identifier which requires brackets.
  • In the filter SQL designer, disabled expressions are now correctly omitted from the filter.
  • Renaming a group from the Group Navigator now works.
  • Renaming a group in the Group Properties dialog now updates the group name in the Add To Group context menu.
  • Error when adding the same object to a group more than once is fixed (duplicate object).
  • Using Add To Group | New Group now saves the group correctly if only one object is added to the group.
  • Eliminated flickering in the Row Inspector when refreshing the worksheet data.
  • Removed the script display from Properties when a database view is loaded into a worksheet. The view script is available by opening a script worksheet for the database view.
  • If viewing the Properties of a worksheet and then load a new table into the worksheet, the worksheet now stays in the Properties view instead of switching to the Data Grid view.
  • The Data Grid now correctly displays checkboxes for bit data fields when the data is readonly.
  • The Data Grid now correctly word wraps long text data fields when the data is readonly.
  • Deleting a private view that applies to the current worksheet now removes the private view from the worksheet's dropdown list.
  • Private views now work with filters.
  • Renaming a private view from the Properties dialog now updates the view name in the navigator.
  • Changing a private view's scope from the Properties dialog now updates the view in the navigator.
  • Renaming a private view from the navigator now works.
  • In the Properties view of a table worksheet, selecting an object from the relationships chart caused an access violation.
  • Open data in multiple worksheets at one time.
  • Full-featured SQL query editor including SQL auto-completion. Write any SQL query you wish and use powerful data grid features to examine the returned data.
  • Drag-and-drop column grouping. Group data by columns simply by dragging a column from the grid to the Group By box.
  • Full-featured text editor available for all character data fields including Text and NText.
  • Full-featured binary editor available for Image, Binary, and Varbinary fields.
  • Make global changes to multiple rows at once with the point-and-click Multi-Row Update.
  • Improved point-and-click filtering. Expanded and refined to be even easier to use than ever before. Setup complex filters without writing a single line of SQL.
  • Improved private views let you customize data results any way you wish and save that criteria so it can be easily recalled at any later time.
  • Filter by Selection enabled in the grid right-click menu. This function automatically filters the data to show all rows where the current column value matches the currently selected row.
  • Filter Excluding Selection enabled in the grid right-click menu. This function automatically filters the data to show all rows where the current column values does not match the currently selected row.
  • Changes made to the display through the Show/Hide Columns dialog are not longer applied immediately in the data grid. Changes are not applied until the OK button is clicked. Changes can be abandoned by clicking the Cancel button.
  • Cancel Filtering option added to the grid right-click menu.
  • Once connected to a server, if you tried to connect to a new server and failed to login properly, you would remain in the original server. However, as you tried to change databases on the original server, OmniView reported an invalid login error. It was retaining the failed login username and password and trying to use it with the original server connection.
  • Columns with spaces or nonstandard characters in their names caused errors.
  • "Move Down" button in Show/Hide Columns dialog did not do anything.
  • When the filter panel first pops up, the Use Designer button is selected by default, but the remaining designer buttons did not appear. You had to click Use SQL, then click Use Designer again to force the toolbar to show all the designer buttons.
  • The Export option in the File menu did not take you to the Export dialog. You had to use the Export toolbar button.