Q+E Database Editor 5 for Windows 
READ.ME File




This file contains information on the following subjects:

	INSTALLATION PROCEDURE
	WHAT'S NEW WITH VERSION 5!
	NEW DATABASES SUPPORTED WITH VERSION 5.0.3
	KNOWN PROBLEMS WITH Q+E AND SYBASE NET GATEWAY FOR DB2
        LIMITATIONS OF NETWARE SQL        
        CORRECTIONS TO DOCUMENTATION
	USING Q+E WITH C
	USING Q+E WITH ASYMETRIX TOOLBOOK
	USING Q+E WITH MICROSOFT EXCEL
	USING Q+E WITH MICROSOFT WORD FOR WINDOWS
	USING Q+E WITH LOTUS AMI PRO 1.0


--------------------------------------------------------


INSTALLATION PROCEDURE:

	Q+E Database Editor 5 includes a Setup program that 
	installs the executable (.EXE) files, database drivers, 
	and sample files on to your computer .  The Setup 
	program is a Windows program.  To install Q+E Database 
	Editor 5, insert Disk 1 into drive A:, pull down the 
	File menu in the Windows Program Manager and choose the 
	Run command.  In the Run dialog box, type:

		A:\SETUP <ENTER>

	If you install from a drive other than A:, modify the 
	above command accordingly.


--------------------------------------------------------


WHAT'S NEW WITH VERSION 5!:

	This release includes an updated user interface, a 
	customizable icon bar, a Form Designer, a Query 
	Builder, page headers and footers for customizing 
	printed reports, column format masks, subtotals, 
	support for dynamic queries, and an enhanced Microsoft 
	Excel add-in macro (QE.XLA).
	
	If you are upgrading from a previous version of Q+E 
	Database Editor, please be aware that you must 
	highlight the database drivers that you want to install 
	in the database drivers list.  The first time you run 
	the setup program, it will select all of the database 
	drivers. Any subsequent times you run the setup program 
	it will select only the drivers not specified in the 
	SQLCONNECT section of your QEX.INI file.

--------------------------------------------------------
                  
NEW DATABASES SUPPORTED:

Version 5.0.3 of Q+E now has support for the following database systems:
-INFORMIX
-PROGRESS
-Paradox 4.0 files

Obtaining a PROGRESS Driver
--------------------
Q+E supports the following network protocols for PROGRESS:
-NETBIOS
-SPX
-TCP/IP
The PROGRESS driver included on the Q+E release disk 
supports NETBIOS, SPX, and FTP TCP/IP. 
NOTE:  If you use LAN Workplace TCP/IP, Wollongong TCP/IP, or 
HP TCP/IP, you must send in the coupon enclosed in the product 
box so that Pioneer Software can send you the appropriate driver.

Gateways
--------------------
MultiLink/VB can access the following database systems by using an 
existing Q+E database driver and a gateway.
- HP IMAGE/SQL
- HP ALLBASE/SQL
- Teradata
- AS/400 (SQL/400)
- SQL/DS
The following table gives the correct database driver and gateway 
that you must use to access these database systems with Q+E.

DATABASE               DATABASE 
SYSTEM                 DRIVER                GATEWAY
-----------------      -----------------     -----------------
HP IMAGE/SQL           SQLBase               Gupta's SQL Network

HP ALLBASE/SQL         SQLBase               Gupta's SQL Network

Teradata               DB2                   MicroDecisionware 
                                             running on an OS/2 
                                             server

SQL/400 (AS/400)      OS/2 Database Manager  IBM Distributed 
                                             Database Connection 
                                             Services/2 (DDCS/2)

SQL/DS                OS/2 Database Manager  IBM Distributed
                                             Database Connection 
                                             Services/2 (DDCS/2)

---------------------------------------------------------

KNOWN PROBLEMS WITH Q+E AND SYBASE NET GATEWAY FOR DB2

    1.	When you log on to DB2, your Logon ID (user ID) must match the 
        table ownership of tables you are trying to access. If it does 
        not, column names will not be retrieved. If you receive one of 
        the following warnings, the Q+E features that require column names 
        do not work (Query Builder and any dialog box that lists column names).
	
        Warning - No fields found for: tablename
        Query Builder warning #9029
	Warning - Table does not exist: tablename
        Q+E warning # 2942
	
        You can check the ownership of column names by executing the 
        following stored procedure:
	
        exec sp_columns "tablename", "%"
	
        If no column names are returned, contact your system administrator.

    2.  When you create a new table definition using the File Define 
        command, Q+E reports a warning stating that the table does not 
        exist. To work around this error, click OK and when the Save As 
        dialog box appears, click Cancel and then click No in the dialog 
        box that asks you if you want to save the changes you have made. 
        The new table is created.

    3.  The data types Long Varchar and Timestamp are returned incorrectly 
        from the Sybase stored procedure sp_datatype_info as LONGVAR and 
        TIMESTMP. (We are working with Sybase to solve this problem.) In 
        Define Windows (File Define command), these wrong data types are 
        listed in the TYPE drop-down list. To work around this error, you 
        must use the File SQL command to display the SQL dialog box and type 
        in the Create Table statement with the correct spelling for these 
        data types.

---------------------------------------------------------

LIMITATIONS OF NETWARE SQL

     NetWare SQL imposes restrictions on the physical structure of records 
     that may cause problems when you try to save an existing table from 
     another database source (such as, dBASE, Oracle, etc.) to NetWare SQL. 
     The restrictions are
     
     1.  The sum of all fields for a record may not exceed 32767 bytes in 
         width or the defined length of the datalength parameter for a 
         user’s installation.

     2.  Only one (1) Long Varchar field is allowed in any given table, 
         and it must be the last field in the record.

     Problems can arise because the table being converted over may be 
     incompatible with these restrictions. For example, dBASE memo fields 
     are mapped to NetWare SQL as 32767 length fields. This will work if 
     the table has only one memo field, but additional fields in the table 
     would cause the definition to exceed the maximum size.

     One possible work around is to save (File Save As command) the source 
     table to another table of the same source and then modify the column’s 
     datatypes to be more compatible with NetWare SQL. For example, you 
     could convert a memo field (Varchar) to a fixed length character field 
     large enough to hold the records. This avoids the use of the Long Varchar 
     in NetWare SQL and reduces the total record length.

--------------------------------------------------------

CORRECTIONS TO DOCUMENTATION:

	The following information was incorrectly stated or 
	inadvertently left out of the October 1992 and/or
        November 1992 User's Guide. The May 1993 printing of
        the manual corrects these problems.


	Chapter 5 - Defining Page Layout for Printed 
	Reports:
		
		The default page headers and footers are not 
		the same as those shown.  
		Please see the online help for the correct 
		information.


	Chapter 10 - Using Q+E With Other Applications:

		At the bottom of page 166, Step 3 should 
		read:

		3.  Move to the directory that 
		    contains the QE.XLA file.  By 
		    default, this is the C:\QE\EXCEL 
		    directory.
                
                The QE.XLA macro supports five additional macro 
                functions than those listed and described in Chapter 10. 
                They are: DB.DELETE, DB.LOGOFF, DB.OPTIONS, 
                DB.OPTIONS.DBASE, and DB.OPTIONS.TEXT.
                Please see the online help for information
                about these macro functions.
	
	Chapter 11 - Using Dynamic Data Exchange (DDE)

		As described in Chapter 11 of the User's Guide, 
		the DDE Initiate function is used to open a 
		channel between a Client application and a 
		Server application.  The Initiate function has 
		two parameters, the Server application name and 
		the Topic.  The User's Guide indicates that an 
		error will be returned if the Topic is not valid.
		Q+E has been modified so that an error will 
		not be returned to Initiate when the Topic is 
		invalid.  Instead, the DDE channel will be opened
		successfully.  However, an error will be returned
		to any subsequent DDE operation (Request, Poke, 
		or Execute) attempted on the channel.  DDE 
		Terminate should be used to close the channel.

		THE OPEN EXECUTE COMMAND:  When EXECUTING the 
		OPEN command, the first parameter to OPEN must 
		be a complete SELECT statement for server 
		databases.  The first parameter to OPEN cannot 
		simply be a table name.


	Chapter 12 - Using Q+E Commands
		
		SUBTOTALS and TOTALS commands:  The correct 
		values for the parameter separator_n are:

			0	Blank line
			1	Dashed line
			2	No separator


		New Command:  A new command "SQL.EDIT.TEXT" 
		was inadvertently left out of the 
		documentation.  This command can be included 
		in a customized icon to allow direct access 
		to the SQL text for a query. The format of 
		the command in the icon's action is:

			SQL.EDIT.TEXT? ()


		Pattern-Matching:  The DOS wildcard 
		characters '*' and '?' can only be used for 
		the Like and Not Like operators in the Add 
		Condition dialog box or in QBE (Query By 
		Example) mode in a form.  Whenever Like or 
		Not Like is specified in a SQL statement the 
		ANSI standard pattern-matching characters '%' 
		and '_' must be used.


		The level_n parameter for the EDIT.BREAK command
		is missing from the documentation.  The command is

		EDIT.BREAK (level_n, sort_n, separator_n, dup_l)

		where level_n determines which break is to be
		modified.


	Chapter 14 - Btrieve Databases
                
		If you are using Btrieve 6.0 or higher and accessing
		a Btrieve database located on a network, you need
		to use the network version of WBTRCALL.DLL (not the
		WBTRCALL.DLL shipped with Q+E for local access of
		Btrieve files).

	Chapter 16 - dBASE-Compatible Database Files

		The Q+E Database Editor 5 dBASE driver now 
		supports open file caching for increased 
		performance.  dBASE files opened from Q+E 
		Database Editor 5 are not closed when the 
		query window is closed. If another 
		application (including Q+E Database Editor 5) 
		tries to open these dBASE files exclusively, 
		they will receive an error message stating 
		that the file is in use.  The user can 
		specify the maximum number of open files that 
		will be cached by a QEX.INI setting in the 
		dBASEFile section.  The setting name is 
		'FileOpenCache'.  For example, if the user 
		wants to cache three open files, the 
		following line can be added to the QEX.INI 
		file:

			FileOpenCache=3

		To disable file open caching, set 
		FileOpenCache to 0.  The default for the 
		number of open files that are cached is 4.


	Chapter 18 - INGRES Databases

		In order to access INGRES database systems, 
		Q+E Database Editor 5 requires:

			INGRES for Desktop Computers

			Networking for DOS/Networking for 
			Windows
			
			Release: 6.4/01 (net.msd/00) 6.4/01 
			(net.win/02)

		The INGRES driver now allows the user to 
		enter SET statements using the File SQL 
		command.  This allows the user to set various 
		session options such as LOCKMODE.


	Chapter 22 - Paradox Database Files

		When encrypting existing Paradox files, the 
		User's Guide states that you can issue the 
		ENCRYPT statement from the Open dialog box 
		using the SQL Query window.  You can no 
		longer execute an SQL statement through the 
		Open dialog box.  To execute an SQL 
		statement, use the File SQL command, type in 
		the statement, and click the Execute button.


--------------------------------------------------------


USING Q+E WITH C:

	Q+E Database Editor 5 includes the files needed to use 
	the Q+E Connect library.
	
	Q+E Connect consists of the following files:
	
		QECON.DLL	Connect routines
		QECON.LIB	Import library for QECON.DLL
		QECON.H		C include file that contains the 
				function definitions for the 
				exported routines
		QE.TBK		Sample Toolbook application that 
				uses QECON.DLL


	For C Programmers

		QECON.DLL can be called from C programs.  Using 
		Q+E Connect eliminates the need to code DDE 
		support into your application.  Q+E Connect 
		handles all the DDE activity for you.
		
		To include QECON.DLL calls in your C code, you 
		need to include the function definitions specified 
		in QECON.H.  The following line will include the 
		function definitions:

			#include "qecon.h"

		You will also need to reference the Q+E Connect 
		import library QECON.LIB in the library section of 
		your link line or link response file.  For 
		example:

			link winmain,appname/align:16,,libw 
			qecon,app.def


--------------------------------------------------------


USING Q+E WITH ASYMETRIX TOOLBOOK:

	Q+E Database Editor 5 includes the files needed to use 
	the Q+E Connect library.

	Q+E Connect consists of the following files:

		QECON.DLL	Connect routines
		QECON.LIB	Import library for QECON.DLL
		QECON.H		C include file that contains the 
				function definitions for the 
				exported routines
		QE.TBK		Sample Toolbook application that 
				uses QECON.DLL


	For ToolBook Users

		The only file required to use the Q+E Connect 
		routines from Toolbook is QECON.DLL.  This file 
		needs to be copied into your Windows system 
		directory, or into any other directory on your DOS 
		PATH.

		The disk also contains QE.TBK, a sample ToolBook 
		application that accesses database files using 
		QECON.DLL and Q+E Database Editor 5.  QE.TBK 
		accesses the sample dBASE-compatible database 
		files shipped with Q+E Database Editor 5, DEPT.DBF 
		and EMP.DBF.

		To run QE.TBK, first start Q+E Database Editor 5.  
		Use the File Open command and make sure that 
		EMP.DBF and DEPT.DBF appear in the File List in 
		the Open Dialog box.  Change directories if 
		necessary so that they are in the File List.
	
		Then run ToolBook, and open QE.TBK.

		QE.TBK contains three pages.  You can change pages 
		by clicking the arrows at the bottom left of the 
		page.

		The first page displays Department records at the 
		top of the page, and the Employees in the current 
		department, listed below.  You can move through 
		the departments by clicking the Next Dept and 
		Previous Dept buttons.

		The second page lets you query Employee records.  
		Click the Do Query button to return all employee 
		records.  When Employee records are being 
		displayed, you can click the department ID value 
		to bring up a window displaying information about 
		that department.  Click Enter Query to re-enter 
		query mode.  In Query Mode, you can enter values 
		in the fields.  Then when you click Do Query, only 
		records that match those values will be returned.  
		You can also use the following operators in front 
		of the value:

			>       Greater than
			>=      Greater than or equal to
			<       Less than
			<=      Less than or equal to
			<>      Not equal

		For example, if you enter >20000 in the Salary 
		field and click Do Query, employees earning 
		greater than $20000 will be retrieved.  The third 
		page lets you individually exercise the Q+E 
		Connect functions. There is a button for each 
		function in QECON.DLL.  Beside each button are 
		fields in which you enter the parameters for the 
		function.  This page can be used to help you learn 
		Q+E Connect and help you debug your Q+E Connect 
		programs.


--------------------------------------------------------


USING Q+E WITH MICROSOFT EXCEL:

	Q+E Database Editor 5 includes an add-in for Microsoft 
	Excel 4.0 named QE.XLA.  The Setup program copies this 
	file to the install directory.  To use the add-in, use 
	Excel's File Open command and open QE.XLA.
	
		Note: The QE.XLA add-in requires Microsoft Excel 
		version 4.0 or later.  It will not work with older 
		versions.

	Before you open QE.XLA, you first need to make sure 
	that you do not have the version of this add-in 
	installed that was shipped with Excel 4.0.  To check if 
	the Excel version has been installed, use Excel's 
	Options Add-ins command.  If "Q+E Integration Add-in" 
	appears in the list of installed add-ins, click the 
	Remove button to remove it from the list.
	
		Note: If the Add-ins command does not appear in 
		Excel's Options menu, you will have to remove the 
		Q+E Integration Add-in by editing the EXCEL4.INI 
		file in your \WINDOWS directory.  Use a text 
		editor, edit EXCEL4.INI, and remove all lines from 
		the following sections that start with the letters 
		QE:

			[Delete Commands]
			[Init Commands]

		Also, in the [Microsoft Excel] section, delete any 
		lines that begin with OPEN and contain QE.XLA.
	

--------------------------------------------------------


USING Q+E WITH MICROSOFT WORD FOR WINDOWS:

	Q+E Database Editor 5 includes a Word for Windows 
	template file named QE.DOT.  The Setup program copies 
	this file to the directory in which you installed Q+E 
	Database Editor 5.  To use this template, you must copy 
	QE.DOT to your Word for Windows directory (commonly 
	C:\WINWORD).

	QE.DOT adds commands to the Word for Windows Tools menu 
	which make it easy to generate form letters and address 
	labels using data from Q+E Database Editor 5.  For more 
	information, you may want to read the Merging Documents 
	section in the Microsoft Word for Windows User's 
	Reference.

	The general steps to build a form letter are:
	
		1) Use Q+E Database Editor 5 to build a query 
		which retrieves the names, addresses, etc. that 
		are to be included in the form letter.  Save the 
		query to a query file (.QEF file).

		2) Run Word for Windows.  Use the File New 
		command.  In the dialog box, choose Document (not 
		Template) as the type, click QE in the Use 
		Template list box, and click OK.  This opens a new 
		document that uses the QE.DOT template file.

		3) Pull down the Tools menu and choose Set Q+E 
		Query.  A dialog box appears in which you enter 
		the name of the Q+E query file you built in step 
		1.  You can change directories in this dialog box 
		by entering the path of the new directory.
		
		4) Type in the form letter.  Position the cursor 
		at each place you want to insert a value from the 
		database, and use the Tools Paste Q+E Field 
		command.  This may ask if you want to start Q+E.  
		If it does, click Yes.  

		A dialog box displays the fields from the Q+E 
		query file.  Click a field and click OK.  That 
		field name will appear in your document enclosed 
		in { }.  (Note: you can't type in {name}, you must 
		use this command or the Word for Windows Define 
		Field command.)
	
		5) To generate form letters with the actual data 
		substituted for the fields, use the Tools Print 
		Merge with Q+E command.  When you click New 
		Document, Word for Windows will generate the form 
		letters using the data retrieved from Q+E.  The 
		new document can be saved or printed.

	You can also retrieve data from Q+E and place it 
	directly in a Word for Windows document.  The general 
	steps to do this are:

		1) Use Q+E to build a query which retrieves the 
		records to be included in your document.  Save the 
		query to a query file (.QEF file).

		2) In Word for Windows, position the cursor where 
		you want the records included and use the Tools 
		Paste Q+E Records command.  This command will 
		retrieve the data from Q+E and paste it into your 
		document.

	In addition to the QE.DOT template, the techniques 
	described in Chapter 10 of the Q+E User's Guide can be 
	used to integrate the database capabilities of Q+E with 
	Word for Windows.


--------------------------------------------------------


USING Q+E WITH LOTUS AMI PRO 1.0:

	The Q+E disk contains a Lotus/Samna AMI Professional 
	macro file named QE.SMM.  This macro adds commands to 
	the AMI menu which allow you to perform mail merges 
	with information from Q+E.  Please note that this macro 
	only works with Lotus/Samna AMI Professional version 
	1.0.

	The Setup program copies this file to the install 
	directory.  To use this template, you should copy 
	QE.SMM and QE_AMI.EXT to your AMI Pro macros directory.

	Before you use the AMI macro, run Q+E and build a query 
	which retrieves the names, addresses, etc. that are to 
	be included in the form letter.  Save the query to a 
	query file (.QEF file).

	While running AMI Professional, load the macro by 
	following these steps:

		1) Pull down the Tools menu.
		2) Choose the Macros command.
		3) Click QE.SMM in the Macros command dialog box, 
		then click OK.
		4) The macro will be opened and a new Q+E Menu 
		option will be added to the menu bar.

	Next, you choose the Q+E query file whose results are 
	to be included in the form letter:

		1) Pull down the Q+E menu in AMI.
		2) Choose the Set Q+E Query command.
		3) In the dialog box, type in the full path name 
		to the Query file or click on the file in the list 
		box.
		4) Click OK.  The macro will create a definition 
		file that will be used in later steps.

	Type the form letter.  In the places where you want to 
	substitute data from the database, paste a field name 
	by following these steps:

		1) Place the cursor where you wish to paste a 
		field.
		2) Pull down the Q+E menu.
		3) Choose the Paste Q+E Field command.
		4) Click the field you wish to paste in the list 
		box and click OK.

	Once the form letter has been completed, you merge the 
	data file with the document by following these steps.

		1) Pull down the Q+E menu.
		2) Choose the Merge to File command.
		3) Enter the name of the file with which you wish 
		to merge.  This file will contain the resulting 
		form letters with database values substituted in 
		the designated locations.
		4) Click OK.

	The Q+E disk also contains the files necessary to 
	modify the QE.SMM macro dialog boxes.

		QE_AMI          make file
		QE_AMI.DLG      dialog box definition file
		QE_AMI.RC       resource file
		QE_AMI.DEF      definition file


--------------------------------------------------------


End of READ.ME file
