FastTips: Interoperability Questions & Answers

PSS ID Number:  Q100850
Article last modified on 08-27-1993

1.00 1.10
WINDOWS

======================================================================
  Microsoft® Product Support Services Application Note (Text File)
 WX0811: INTEROPERABILITY WITH OTHER APPLICATIONS QUESTIONS & ANSWERS
======================================================================
                                                   Revision Date: 5/93
                                                               No Disk
The following information applies to Microsoft Access, version 1.0
Copyright 1993.
 ---------------------------------------------------------------------
| INFORMATION PROVIDED IN THIS DOCUMENT AND ANY SOFTWARE THAT MAY
|
| ACCOMPANY THIS DOCUMENT (collectively referred to as an Application
|
| Note) IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
|
| EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED
|
| WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR
|
| PURPOSE. The user assumes the entire risk as to the accuracy and
|
| the use of this Application Note. This Application Note may be
|
| copied and distributed subject to the following conditions: 1) All
|
| text must be copied without modification and all pages must be
|
| included;  2) If software is included, all files on the disk(s)
|
| must be copied without modification (the MS-DOS®  utility
|
| diskcopy is appropriate for this purpose);  3) All components of
|
| this Application Note must be distributed together;  and  4) This
|
| Application Note may not be distributed for profit.
|
|
|
|   Copyright © 1993 Microsoft Corporation.  All Rights Reserved.
|
|   Microsoft, FoxPro, Microsoft Access, and MS-DOS are registered
|
|   trademarks and Windows is a trademark of Microsoft Corporation.
|
|    Paradox is a registered trademark of Ansa Software, a Borland
|
|                               company.
|
|       dBASE and dBASE IV are registered trademarks of Borland
|
|                         International, Inc.
|
|   This document was created using Microsoft Word for Windows™.
|
 ---------------------------------------------------------------------
1.  Q. When I export a Microsoft Access table to SQL Server and then
       reattach it to Microsoft Access, I can't edit the data. Why
       does this problem occur?
    A. Microsoft Access can update an attached SQL Server table only
       if the table has a unique index. However, Microsoft Access does
       not build SQL Server table indexes, unique or otherwise, when
       you export data; Microsoft Access allows you only to export
       data to SQL Server back ends. For example, if you attach the
       table immediately after exporting data to it from Microsoft
       Access, the data is displayed in Datasheet or Form view as
       read- only; therefore, updates to the exported table's data are
       not allowed.
       To work around this problem, you must create the SQL Server
       table indexes manually after you export the data from Microsoft
       Access to SQL Server. After the SQL Server indexes are created,
       you can create forms based on the attached SQL Server tables
       and update the data.
       For information on creating indexes based on SQL Server
       database tables, see the "Microsoft SQL Server System
       Administrator's Guide", or pages 67-72 in the "Microsoft SQL
       Server Language Reference".
2.  Q. How do I link a Microsoft Access table to a Microsoft Excel
       spreadsheet using dynamic data exchange (DDE)?
    A. The easiest way to use DDE is to create a paste link between
       Microsoft Access and Microsoft Excel. To do this, use the
       following steps:
       1. In the Microsoft Access Database window, highlight the table
          you want to link to Microsoft Excel.
       2. From the Microsoft Access Edit menu, choose Copy.
       3. From the Microsoft Excel Edit menu, choose Paste Link.
       The formula resulting from the Paste Link command should look
       like the following example
          {=MSAccess|'NWIND.MDB;Table <Customers>'!All}
       where <Customers> is the name of the table you copied.
       For more information on linking Microsoft Access data to data
       in other applications, see the "Microsoft Access User's Guide",
       version 1.0, Chapter 13, "Using Pictures, Graphs, and Other
       Objects," pages 337-339.
3.  Q. Why do I get a "database corrupted" error message when I try to
       import a Paradox® database into Microsoft Access?
    A. When you import a keyed Paradox table into Microsoft Access,
       you must place it in the same directory as its associated index
       file. Because Paradox stores information about a table's
       primary key in the .PX file, it is important to verify that the
       .PX file is present before you import the Paradox table.
       If the index (.PX) file is not found, the following error
       message appears
          <filename>#DB' is corrupted or isn't a Microsoft database
       where <filename> is the name of your Paradox table.
       If a Paradox table and its associated index file become
       separated, or if the .PX file becomes corrupted, Microsoft
       Access is unable to import the table. To recreate the index
       file, you must restructure the table in Paradox.
4.  Q. When will I be able to attach Microsoft FoxPro® tables to
       Microsoft Access?
    A. Although Microsoft Access can import Microsoft FoxPro tables,
       it currently cannot attach most FoxPro tables. However,
       Microsoft Access can attach a FoxPro table as a dBASE IV®
       table if BOTH of the following conditions are met:
       - The FoxPro table does not have any memo fields in its
         structure.
       - The FoxPro table is attached without any FoxPro index files.
       If either of the above conditions is not met, the FoxPro table
       must be imported, rather than attached, to Microsoft Access.
       The reason for this is that although FoxPro uses a .DBF file
       structure similar to that of dBASE®, the memo and index
       structures of FoxPro and dBASE .DBF files are different.
       Microsoft is currently working on a Microsoft Access driver for
       FoxPro that will allow you to attach all FoxPro tables in their
       original formats. When the driver is complete, Microsoft will
       make it available free of charge.

Additional reference words: 1.00 1.10 ivr ivrfax fasttips
KBCategory:
KBSubcategory: GnrlNw