This action might not be possible to undo. Are you sure you want to continue?
0 ----------------------------------------------------------(c) Copyright Microsoft Corporation, 1998 Release Notes January 19, 1998 Welcome to the release of the Visual FoxPro ODBC Driver! Please read this import ant information. System Requirements -----------------------How to Use This Document -----------------------To view the ReadMe file in Windows Notepad, maximize the Notepad window and clic k Word Wrap on the Edit menu. To print the ReadMe file, open it in Notepad or an other word processor, and then use the Print command on the File menu. -------CONTENTS -------1. INSTALLATION NOTES 1.1 System Requirements 1.2 What's New in this Release 1.3 Installing the Driver 1.4 Adding a Data Source 1.5 Help Files 1.6 Naming Conventions Supported Areas 2.1 Language Support 2.2 ODBC 2.5 Compliance 2.3 Referential Integrity 2.4 Thread Support 2.5 dBase® Support 2.6 International Support UnSupported Areas Known Issues Troubleshooting Books
3. 4. 5. 6.
1.1 System Requirements ======================== To install the Microsoft(r) Visual FoxPro(tm) ODBC driver, you need: * Windows NT 3.51 (or later. Service Pack 5, recommended) or Windows 95 (or later). * 2 MB disk space. Important: Visual FoxPro ODBC Driver 1.0 is a 32-bit driver only. Windows 3.1 a nd Windows for Workgroups platforms are not supported.
5. double-click the 32-bit ODBC icon.DLL is smaller (from 1.5 Help Files ========================== The Visual FoxPro ODBC driver comes with two help files.1. 1. define a data source: 1. 1. In the ODBC Visual FoxPro Setup dialog box.F. Enter the name of the database or the path to the free table.5 compliance if necessary.HLP . * If you insert or update a table with a logical field (a column with a SQL_BIT data type).T. Select either Visual FoxPro database (. When comparing values or in an expression. 2. Click OK and then click Close. (fals e).DBC) or Free Table directory.2 What's New in this Release ========================= * Query performance is 20% faster. you can now use 1 (true) and 0 (false) to store a value in a field. Select Microsoft Visual FoxPro Driver. Click Add.4 Adding a Data Source ========================= After installing. 6. Note: The Visual FoxPro ODBC Driver installation updates the ODBC components to ODBC 2.5 components. * SQLGetInfo( ) and SQL_FILE_USAGE now returns SQL_FILE_QUALIFIER for both datab ase and free table data sources.TXT file in your Windows sy stem directory for additional information on enhancements or features of the ODB C 2.0) now works with the Visual FoxPro ODBC Driver. enter a data source name.6 Naming Conventions ========================== . In Control Panel. 7.General ODBC information which contains information on: * The ODBC driver dialog box * The options that can be set in the drivers dialog box in the Control Panel * DRVVFP. (true) and . * The SET commands (see Help file for a list of supported SET commands) are now supported * VERSION( ) is supported through stored procedures. * The 16-bit version of Microsoft Query (version 1. run SETUP. 3. located in the SYSTEM d irectory on Windows 95 or the SYSTEM32 directory on Windows NT: * ODBCINST. * VFPODBC. 1.3 Installing the Driver ========================= To install the Visual FoxPro ODBC Driver. you must use . See the README25.HLP Visual FoxPro ODBC Driver Help file which provides information on: * Installing and Configuring * Using the Visual FoxPro Driver * Technical Reference * ODBC API * Visual FoxPro Language Reference * Error Messages 1. 4.20MB to ~835KB). * Local views are read-only. or click Browse .EXE.
however. use the AS clause. and defaul t values. Supported Areas ========================== The following section describes areas of particular support by the Visual FoxPro ODBC driver. See the Help file. i f you execute the following statement: SELECT MIN (customer_id) FROM customers the Visual FoxPro ODBC Driver returns min_customerid as the name of the column i n the result set.HLP.2 ODBC 2. documents supported functions and acceptable input parameters. Local views based on parameterized views are not excluded. Ple ase report any problems you find regarding the APIs. The Help file.4 Thread Support ========================== The driver is thread-safe. not free tables.x and Visual FoxPro tables. 2.3 Referential Integrity Support ========================== The Visual FoxPro ODBC driver supports Visual FoxPro rules.5 Compliance ========================== The Visual FoxPro ODBC driver is ODBC Level 1 API compliant and also implements several Level 2 APIs. 2. Remote Views and Parameterized Views Any time SQLTables( ) is called. The Visual FoxPro ODBC driver can process queries in the background. DRVVFP. If you would like to control the resulting field name. For example. All supported APIs have been implemented at this time.HLP. the Visual FoxPro ODBC Driver allows you to access tables that are in a Visual FoxPro database container (. but will generate errors if you use them. In addition. triggers. FoxPro 2. see the "ODBC Visual FoxPro Setup Dialog B ox" Help topic. as in this example: SELECT MIN(customer_id) AS minimum_custid FROM customers ========================== 2. you will find views (if they are present) so you can check for name conflicts.DB C file). If you call SQLTables( ) with a unique table na me. remote and parameterized views are excluded fro m the list. For more information. provided they contain functions that are supported by the driver.The Visual FoxPro ODBC Driver names columns based on expressions. See th e Visual FoxPro Language Reference for the extended grammar. FoxP ro 1.DBC file).x. 2. DRVVFP.1 Language Support ========================== Supported Versions of FoxBase+ and FoxPro Tables The Visual FoxPro ODBC Driver gives you access to Microsoft(r) FoxBase+(r). Note The Visual FoxPro ODBC Driver only allows transactions on tables within a Visual FoxPro database (. . for details on which Visual FoxPro language elements are supported. 2. Also. Visu al FoxPro SQL extends the SQL functionality available through the driver.
x: The files are read without conversion. * If a table is opened exclusively and the same table is accessed by another use r with SET EXCLUSIVE OFF. Unsupported Areas ========================== * Refresh is not supported in rules and triggers. The default collating sequence is "MACHINE".NDX) .MDX.6 International Support ========================== * The driver is DBCS enabled.x file has associated index files (. Known Issues ========================== * If you insert. 42-44). local views (non-parameterized) are fully supported. you might get a "Trigger Failed" message. * dBASE(r) v4.x and 5. Any command or function not listed in the Help file is not supported. * dBASE(r) v4. and lists the un supported commands and functions. ========================== 4. the collating sequences on Eastern European code page machines will not work. The dBASE(r) files are supported in the following manner: * dBASE(r) v2. ========================== 3.x: If the files do not have memo fields and the table has fewer than 255 columns. Note The FOXPRO. Check for unsupported comm ands in the trigger. then the error "Option Value Changed" is returned by V . the files are read. . or update a Visual FoxPro table via the Visual FoxPro O DBC driver. or by selecting a different collating sequence from the driver opti ons in the Data Source Setup dialog. however. If it is remove d. These files should be accessed read-only.5 dBase® Support ========================== Supported Versions of dBASE(r) IV Tables The Visual FoxPro ODBC Driver gives you access to dBASE(r) 4 and earlier tables. * The Help file describes the supported commands and functions.x tables with memo fields: These files require conversion in the full Visual FoxPro for Windows product before using them with the Visual FoxPro ODBC Driver. * You can now set the collating sequence for index ordering. by calling SQLPrepare( ) and SQLExec( ) (see the ODBC SDK Reference manua l p.INT file is installed in the system directory. * INDEX ON is not supported in this release. Interactive input of a parameter value is not allowed in ODBC.x and 3. The driver will not read or convert files. The collating sequence can be chang ed by executing either a SET COLLATE TO Language with the ODBC C API SQLExecDire ct( ). The list of support ed collating sequences can be found in the description of SET COLLATE in the Vis ual FoxPro Language Reference Help topic.2.x and 5. 2.x or 5. delete. the Visual FoxPro ODBC Driver will not update the file properly and the indexe s will be corrupted. * Remote views to other ODBC data sources are not supported by the Visual FoxPro ODBC driver. * Parameterized views work in a trigger only if the parameter has been assigned a value before the view is opened. Caution If a dBASE(r) v4.
2. For example. Specify a log file name. Now. Specify a When to trace option. Books ========================== Microsoft ODBC 2. 4. double click the 32bit ODBC icon. Click on the ODBC Drivers tab. try the following and then try to rei nstall again: 1. * Use the Microsoft ODBC Data Source Administrator control panel Tracing tab to help determining the cause of problems. To view the versi on: 1. Occasionally. 3. * You can generate an ODBC Trace Log by using the ODBC Data Source Administrator control Panel: 1. Clean-boot the machine. Visual FoxPro does not allow the creation of field names that begin wit h a number. disable these options befo re reinstalling. their input parameter s. but MSQuery does. ========================== 6. copy only the last 4 or 5 functio n calls and paste them into a separate document before sending the bug report. For example. In the ODBC Data Source Administrator control Panel. 3. start in Safe Mode. the field name "1995 Sales" is not allowed. . 5. 2. If the computer has video or system ROM shadowing. 4. If you are still having problems: * Make sure that you are running on a clean configuration when testing issues. double click the 32bit O DBC icon.EXE file is not corrupted. Inside ODBC (ISBN#: 1-55615-815-7 from Microsoft Press) provides a good backgrou nd on the development of the ODBC specifications and a CD with ODBC code example s.isual FoxPro ODBC Driver instead of "File is in use by another. Click Start Tracing Now. Troubleshooting ========================== If you have trouble installing the driver.0 Programmer's Reference and SDK Guide (ISBN#: 1-55615-658-8 fr om Microsoft Press) provides basic reference information. o r toolbars such as Microsoft Office Manager. third-party shells. including virus software. and their output are written to the log file. Check that the . Notepad. Close all other applications. under Windows 95. ========================== 5. Select the Tracing tab. when you execute your code. The ODBC log file is ASCII text that you can view in any standard ASCII text editor such as Word. Since the ODBC trace log can be lengthy. it might be necessary to include the trace log in a bug re port. 2. * Check to see if the latest build of the driver is installed. In the Control Panel." * MSQuery returns a "Cannot Open File" error when creating a table with a field name that starts with a number. all the C ODBC API calls. or W ordPad.
Database Developer's Guide with Visual C++ (ISBN#: 0-672-30613-1 from Sams Publi shing) has several good C++ examples that use the ODBC API. ========================== .
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.