Import each table data in a SQL file to a separate Visual FoxPro table

by

Want to import data from each table in a SQL file to a separate Visual FoxPro table?

Try Withdata FileToDB, a SQL to Visual FoxPro converter, Import each table data in a SQL file to a separate Visual FoxPro table, Easy and Fast.

Download Withdata FileToDB Download FileToDB

Import data from each table in a SQL file to a separate Visual FoxPro table

Select tables in SQL file -> Set Visual FoxPro tables -> Import SQL data to Visual FoxPro

Choose Visual FoxPro and logon.

convert data from each table in a SQL file to a separate Visual FoxPro table - Choose Visual FoxPro and logon

Click “Wizard – 1 File To N Tables” at task dialog.

Import data from each table in a SQL file to a separate Visual FoxPro table - task window

Select the “SQL” file type.

Import data from each table in a SQL file to a separate Visual FoxPro table - select file type

then show the wizard.

1. Open a SQL file, select tables.

Import data from each table in a SQL file to a separate Visual FoxPro table - open SQL file

2. Show existing Visual FoxPro tables, choose “Import Type”.

Import data from each table in a SQL file to a separate Visual FoxPro table - choose import type

3. Set Visual FoxPro tables.

Import data from each table in a SQL file to a separate Visual FoxPro table - set tables

4. Show summary, set “Convert Rows”.

Transfer data from each table in a SQL file to a separate Visual FoxPro table - preview

5. Import data from each table in a SQL file to a separate Visual FoxPro table.

Copy data from each table in a SQL file to a separate Visual FoxPro table - import data

View imported data in Visual FoxPro table

SQL tables to Visual FoxPro converter - view data


More about SQL file to Visual FoxPro converter

SQL → Visual FoxPro reference

Type mapping

Value kindin SQLin Visual FoxPro
IntINTNumeric(10,0)
BigintBIGINTNumeric(19,0)
DecimalDECIMAL(p,s)Numeric(p,s)
FloatDOUBLE PRECISIONFloat
TextVARCHAR(n)Character(n)
Long textTEXT / CLOBMemo
DateDATEDate
DatetimeTIMESTAMPDateTime
BinaryBLOB / BYTEAGeneral
BooleanBOOLEAN / SMALLINTLogical
JSONJSON / TEXT(none)

Dialect differences

SQL is a file format and Visual FoxPro is a database server, so the target has to be told the types the file never carried - the rows below are where the two sides diverge.

Propertyin SQLin Visual FoxPro
port—(file-based)
identifiersTwo competing conventions: single-quoted literals and diale...—
row limit—(driver dependent)
datesDepends on the dialect: DATE literals, TO_DATE(), or plain ...Date (D), DateTime (T)
long text—Memo (M)
binaryDialect-specific: X-quoted literal, 0x hex, or decode()General (G)
separatorStatement terminators (;)—
encodingNo declaration—
typingTypes belong to the target database, and they differ betwee...—
shapeStatements; a dump usually means CREATE TABLE plus INSERT rowsTables of rows and columns
ceilingNo formal limit, but a single INSERT statement has to fit i...—

No counterpart

  • SQL values of kind JSON have nowhere to go in Visual FoxPro.

Convert your data online, free

Free in-browser converters for CSV, Excel, JSON, XML and SQL: Withdata Online Data Conversion. Large files, batch conversion or scheduling? See the offline desktop apps, or browse all data conversion tools.