Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Importing / Linking / April 2005

Tip: Looking for answers? Try searching our database.

Error importing (or linking to) a Foxpro table

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Braveheart - 28 Apr 2005 13:22 GMT
I am in the process of converting VFP 6 applications to Access 2003 (a
temporary measure while the organisation I am consulting for decides on
their new data strategy).

When I try to import some of their VFP tables into Access, I get the
error "the decimal field's precision is too small to accept the numeric
you attempted to add" (this corresponds to Access Error 3761). The
Import aborts without creating the new table in the Access database. One
field in the VFP table has a rather large decimal value stored in it.

Any thoughts anyone might have on this problem would be greatly
appreciated.
Cindy Winegarden - 30 Apr 2005 16:56 GMT
Hi BraveHeart,

I Googled this problem and found the following:

* Update to the latest Jet 4.0 Service Pack.

* Change the data type that the field is assigned to when you import it

* This bug was introduced in the ODBC driver used by Access 2002 and has
never been fixed (or even, AFAIK, been acknowledged by MS). For example, it
also occurs in the OLE DB Provider. You'll be able to get round it by only
using Access 2000 format databases in Access XP when you want to link to a
VFP table that contains offending data.

Signature

Cindy Winegarden  MCSD, Microsoft Visual Foxpro MVP
cindy_winegarden@msn.com  www.cindywinegarden.com
Blog: http://spaces.msn.com/members/cindywinegarden

>I am in the process of converting VFP 6 applications to Access 2003 (a
> temporary measure while the organisation I am consulting for decides on
[quoted text clipped - 8 lines]
> Any thoughts anyone might have on this problem would be greatly
> appreciated.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.