>Hello All,
>
>I am attempting to import data from a VFP table to a SQL Server Table via ODBC.
>
>Normally I can do this without issue but today I have come across a very peculiar foible indeed. I am using VFP 6.0 SP5 and SQL 2000
>
>I have the table I wish to import adn the wider table it orginates from within a local directory. I have created a Microsoft FoxPro VFP (*.dbf) driver and set it to look at tables within that directory.
>
>I went through teh standard SQL Import process, only to find that my slimmer table was not in the list of tables shown within the ODBC connection. Again this is not a problem, odd but not a problem. I use the wider, original, table and use the "Transform" section of SQL import to allocate the fields from the wider DBF to my slim SQL table. By doing this I realise that a numeric field in SQL is to be populated by a character field from Fox... this is why I had created the slimmer dbf, converting any datatypes that should be converetd prior to import.
>
>So I close SQL, back into Fox and I use the table designer to switch the required fields from a character datatype to a Numeric datatype. Close Fox and back into SQL... through the Import wizard, select my ODBC driver only to find that the wider table no longer shows up in the list of dbf files within the ODBC connection.
>
>Has anyone come across anything similar? Could anyone provide any advice on how to resolve this situation?
>
>Many thanks in advance for any help that can be provided.
>
>Regards,
>
>Ben

Ben,
Yes SQL import wizard misses tables and I don't know why. What instead you use VFP upsizing wizard ? It lets you map datatypes and much more flexibilities.
Cetin