XL97: New Database Query (.dqy) File Format

Last reviewed: February 12, 1998
Article ID: Q164729
The information in this article applies to:
  • Microsoft Query 97 for Windows
  • Microsoft Excel 97 for Windows
  • Microsoft Office 97 for Windows

SUMMARY

Microsoft Query 97 uses a new database query (.dqy) file format. This article discusses the new format and how to use it with earlier versions of Microsoft Query.

MORE INFORMATION

The database query format is the default file format that is used when you use the Save command in Microsoft Query 97. For backward compatibility, Microsoft Query 97 continues to support Microsoft Query version 1.0 and 2.0 (.qry) files when you save and load these files. When you open a .qry file and edit it in Microsoft Query 97, features that cannot be represented in the .qry file format are not available. For example, parameterized query functionality is not available because this feature is not available in earlier versions of Microsoft Query. Also, if you create a query in Microsoft Query 97 and use features that are not supported in earlier versions, you cannot to save the .dqy file as a .qry file until you remove the new functionality.

The database query format is designed to be small, simple, and efficient. Note that most of the presentation information that can be saved in .qry files is not retained in the database query. Defaults are substituted for some items, such as window, table, and document positions. When you perform a new query, .qry files are not supported by the Microsoft Excel Run Query command or the Queries tab in the Choose Data Source dialog box.

When you save a query in Microsoft Query 97, Microsoft Query saves a text file with a .dqy file name extension. This text file consists of at least four lines of text that are each separated by carriage returns and line feed characters. Note that these characters typically do not appear in a text editor.

The format of the Database Query file is as follows:

   XLODBC
   1
   <Connection String>
   <SQL String>
   <Parameter names>
   <Parameter data types>
   <Column Names>

where XLODBC is the type, 1 refers to Microsoft Query 97, and the <Parameter names>, <Parameter data types>, and <Column names> lines are tab delimited.

Sample Database Query (.dqy) File

In the following example, text is wrapped to allow you to view it easily. In an actual .dqy text file, the connection string and SQL string text is not wrapped. Each text string appears on an individual line. The following is a sample .dqy file:

   XLODBC
   1
   CollatingSequence=ASCII;DBQ=C:\office97\Office;DefaultDir=C:\office97\
   Office;Deleted=1;Driver= {Microsoft dBase Driver(*.dbf)};DriverId=277;
   FIL=dBaseIII;ImplicitCommitSync=Yes; MaxBufferSize=512;MaxScanRows=8;
   PageTimeout=600;
   ParadoxNetStyle=3.x;ParadoxUserName=admin;Statistics=0;
   Threads=3;UserCommitSync=Yes;
   SELECT CUSTOMER.CUSTMR_ID, CUSTOMER.COMPANY, CUSTOMER.CITY,
   CUSTOMER.REGION FROM CUSTOMER CUSTOMER
   CUSTMR_ID COMPANY CITY REGION

REFERENCES

For more information about using database query (.dqy) files, click the Index tab in Microsoft Query Help, type the following text

   saving queries

and then double-click the selected text to go to the "Save a query" topic.

For more information about running a query from Microsoft Excel, click the Index tab in Microsoft Query Help, type the following text

   dqy files

and then double-click the selected text to go to the "Run a query" topic.

For more information about creating a parameter query from Microsoft Excel, click the Index tab in Microsoft Excel Help, type the following text

   parameter queries

and then double-click the selected text to go to the "Create a query that prompts for criteria" topic.


Additional query words: 8.0 XL97
Keywords : xlquery kbtool kbualink97
Version : WINDOWS:97
Platform : WINDOWS
Issue type : kbinfo


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.