Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
SQL Server Linked Server, VFPOLEDB, and Numeric Fields
Message
De
15/02/2005 13:39:01
 
 
À
Tous
Information générale
Forum:
Microsoft SQL Server
Catégorie:
Autre
Titre:
SQL Server Linked Server, VFPOLEDB, and Numeric Fields
Divers
Thread ID:
00987150
Message ID:
00987150
Vues:
204
Hi All, 

New to Universal Thread, so please forgive me in advance.  :)

Attempted set-up:

   o  Legacy tables in Visual FoxPro 8.  Some of the tables contain Numeric fields
      of varying sizes but with a decimal precision of 2.
   o  SQL Server Linked Server set-up to access the legacy tables using the VFPOLEDB
      driver.
   o  SQL Server database(s) with view(s) referencing the linked servers.

Problems/issues experienced:

   o  Accessing the underlying FoxPro data through the views works fine for tables
      without fields containing the Numerics with specified decimal precision.  
      Regular Numeric fields work fine as well.
   o  However, accessing the tables with the decimal Numerics results in the 
      following error:

      Non-interface error:  Column <fieldname> (compile-time ordinal 18) of object
      <tablename> was reported to have a PRECISION of 6 at compile time and 5 at run
      time.

Research/attempted resolution thus far:

   o  Numeric field in question has a size of 6 with decimal precision of 2.  Some
      of the data in the fields is of size 5 (e.g. 50.00), so I could see the system
      having a problem thinking the data should be "padded" to the full size.
   o  Tried converting all the Numeric fields to Double, and this made things work.
      However, there is concern about being able to reasonably convert all our 
      legacy decimal Numerics into Double.  Also, based on my understanding, it is 
      hard to believe that this could be a general problem with the VFPOLEDB driver 
      since the VFP Numeric type (with decimal places) is so commonplace.
   o  Found another solution that suggested setting the "lazy schema validation" 
      server option on the Linked Server; however, attempting to do this results
      in the following error message:

      The 'lazy schema validation' option is ignored in this version of SQL Server.

Question:

   Anybody else have this problem and/or know how to resolve it?  Workarounds?  
   Solutions?  Suggestions?  Thanks in advance for the help!
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform