Import numeric field from dbf file - field shrinks by 1 digit

For years I have been importing FoxPro dbf files into SQL Server using a SQL procedure. Everything worked fine.

Recently I had to reinstall some of the software. Now, when I import such a file, each numeric field ends up in SQL Server with the numeric fields 1 digit smaller (i.e., a size-7 numeric field becomes size=6). Character fields are unchanged.

Any idea why this is happening and how to correct it?

Len Rodberg
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It did this when you reinstalled SQL Server or FoxPro?  It sounds like the default of the floating point data type has changed somehow.
LrodbergAuthor Commented:
How would one change the floating point default  -- or the way it imports a numeric field? I haven't found anything that changes it.
You may have been doing the import for years, but you haven't told us what version of FoxPro the data is you're importing or what connectivity mechanism you're using to perform the import.  Without more information, we have to just throw up our hands and give up.

[I guess you didn't think this was important enough to place in the FoxPro zone where those folks know more about the nature of Fox data than those in the SQL Server zone.  ??? ]
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

>> I'm using Visual Foxpro 6.0 and importing through the ODBC connection. Does that help?

Do you know which version of the ODBC driver you're using?

Are you adverse to using an OLE DB Provider for VFP which would have better performance?
Here are the links for both the latest ODBC driver and the latest OLE DB Provider for VFP:

Visual FoxPro ODBC Driver
[There were many versions of the ODBC driver, even with VFP6.  VFP6 was involved in five Service Packs, most of which (if not all) included a revision to the ODBC driver.]

Microsoft OLE DB Provider for Visual FoxPro

On the topic of the OLE DB Provider for VFP--

The Visual FoxPro OLE DB Provider includes the following:

Support for most Open Database Connectivity (ODBC) driver functionality from earlier versions of FoxPro

Improved threading model for scalability

OLE DB Provider for Visual FoxPro
LrodbergAuthor Commented:
I downloaded the latest ODBC driver but it gave an unspecified error when trying to install it (I'm running Windows Server 2003).

The driver I am using (which gives the 1-digit-less numeric field) is version 6.000.8167.

Any idea what the problem might be?
That definitely isn't the latest version.  (the latest should end with 8629, I believe).  The one you show looks like it might have been the very first one for VFP6.  They had a lot of fixes since the base product of VFP6 with five service packs following it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.