Product Home
DTM SQL editor Online Documentation Prev Page Prev Page
General
Product profile
Product versions
Database tools
Install software
Upgrade software
Uninstall software
System requirements
How to buy
Product features
User interface
Hot keys
SQL editor
Search and replace
Data export
SQL library
Results viewer
Connect
Quick Start
Direct Connection
Connect to Desktop File
Data Sources
DSN File
OLE DB Connection
Connection Profile
Connection Information
Troubleshooting Guide
Macros: definition and using
Database schema viewer
Find database object
Data editor
Schema object
Filter database schema
Version control
Command line options
Settings and options
SQL builder
SQL builder
Select type of the statement
Specity objects for select
Build WHERE cause
Select tables or views
Select one table or view
Select fields
Set or change values
ORDER BY and GROUP BY
Create table
Create index
Create view
Plug-ins and SDK
Plug-ins and SDK
Data structures
Plug-in sample, sources
Plug-ins Library
General information
Directory by DBMS
MS SQL Server
Run Query Analyzer
Oracle
Run SQL*Plus
General
Insert Module Header
External preprocessor
Run external tool
Run after script execution
Save/Load Hisroty
Send script by e-mail
Simply preprocessor
WinDiff interface
Directory by functions
Editor plug-ins
Insert Module Header
Run external tool
Run Oracle SQL*Plus
Run MS Query Analyzer
Send script by e-mail
Schema plug-ins
Results plug-ins
Common plug-ins
Run WinDiff
Save/Load Hisroty
Preporcessors
External preprocessor
Simply preprocessor
After execution plug-ins
Run after script execution
Information
Licence agreemnet
Technical support
Send feedback
FAQ and tips
Program tutorial
Troubleshooting guide
Glossary
SQL reference
SQL quick reference

Product FAQ, program tips

Frequently Asked Questions

Q: How can I use DTM SQL editor as the external editor for Oracle SQL*Plus ?

A: There are two options: permanent use and single session use. If you choose the permanent use mode, you should create or edit login.sql file in the home directory of SQL*Plus (D:\ORANT\BIN) and insert the following line: DEFINE _EDITOR=<program path>, see below for reference.

WARNING: in the case when the path has spaces, put it into quotation marks; see the second figure.

If you choose the single session use mode, just type

DEFINE _EDITOR=<program path>, for example: 
DEFINE_EDITOR=C:\Program Files\SQLedit.exe

Another way is to select Editor/Define Editor item in "Edit" menu and to type the program path in the dialog box.

Q: What is the easiest way to place query results into MS Excel spreadsheet format?

A: Right click over the page with the results and select "Export". Select "Excel" as your export format.

Q: Are there easy ways to publish the results on the Web?

A: Use HTML export feature. Right click over the page with the results and select "Export". The program saves data in the very basic format, so we recommend you to employ some more powerful HTML authoring tool to edit the data afterwards.

Q: I usually acquire data from several data sources at a time. How could I know which data source I'm connected to?

A: Starting from the version 1.00.84, the program displays the name of the current data source you are connected to, user name and the name of the data scheme in the window title in "DSN/user/owner/database" format. If some of these fields are empty, they are not displayed, but separating '/'s remain.

Tips. Did you know...

You can get quick access to the file or script you edited earlier by using drop-down menues near Load and Run toolbar buttons.

You can use macros to automate entering scenarios.

You can use right mouse button to get access to the context menu in SQL editor or results viewer.

You can select rows, columns or set of cells in the results grid using left mouse button and drag.

You can view Binary Large Objects as binary or as hexadecimal. View "Settings" for more details...

Program can visualize NULL data values as empty strings or as "NULL" strings. See program options for detailed information...

You can view current cursor position at the right side of the SQL Editor status bar.

Program always creates backup (.BAK) file in the same directory to avoid data overwriting.

Program always creates "auto-save" file for the current script before running it to prevent data loss.