Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-10-24 : 08:29:06
|
| Shelley writes "I am sing DTs to move data from sql server to Foxpro.using visual foxpro oledb driverI am explicitly creating a table like:CREATE TABLE `e:\medispan 2\msiref\spec_dse` (`m_drug` N (5,0) NOT NULL, `m_form` C (3) NOT NULL, `dose_units` C (11) null,`ndse_units` C (11) NULL, `ndosage` N (12,3) NULL, `str_mult` N (8,3) NOT NULL, `brand_name` C (35) NULL, `strength` N (12,3) NOT NULL, `m_str_unit` C (11) NOT NULL, `dose_mult` N (8,3) NULL, `bypckg` L NOT NULL )And when I look at Foxpro table structure all the numeric col are 2 morethan what I specified.. mdrug is n(6,0)str_mult is n(10,3)strength is n(14,3)ndosage is n(14,3)dose_mult is n(10,3)WHy is this conversion adding 2 more to the precision of numeric fieldsThanks for any help!!" |
|
|
AjarnMark
SQL Slashing Gunting Master
3246 Posts |
Posted - 2003-10-27 : 13:06:04
|
| I have no idea why it would do that, but in general, I'd think you'd be better off creating the table in Foxpro first, and then just using DTS to populate it. Don't do the table creation through DTS.--------------------------------------------------------Visit the SQLTeam Weblogs at [url]http://weblogs.sqlteam.com[/url] |
 |
|
|
|
|
|
|
|
sql server to foxpro numeric data type conversion