VOOZH about

URL: https://www.cdata.com/kb/tech/hubdb-odbc-foxpro.rst

⇱ Work with HubDB Data in FoxPro


Work with HubDB Data in FoxPro

👁 Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Load HubDB data into a FoxPro database. This article includes full code and a walk-through of the process.

The CData ODBC driver for HubDB enables you to access HubDB data using the ODBC standard. You can use the CData ODBC Driver for HubDB to integrate HubDB data into your FoxPro project. The procedure below provides a walk-through of the included code sample, which saves HubDB data into tables in a FoxPro database.

Connect to HubDB as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

NOTE: Set the 'Map To WVarchar' connection property to FALSE (FoxPro uses the ODBC W API and returns the WCHAR for the value type).

There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

Using a Custom OAuth App

AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

Follow the steps below to register an application and obtain the OAuth client credentials:

  1. Log into your HubSpot app developer account.
    • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
  2. On the developer account home page, click the Apps tab.
  3. Click Create app.
  4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
  5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
    • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
    • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
  6. Click Create App. HubSpot then generates the application, along with its associated credentials.
  7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.
  8. Under Scopes, select any scopes you need for your application's intended functionality.

    A minimum of the following scopes is required to access tables:

    • hubdb
    • oauth
    • crm.objects.owners.read
  9. Click Save changes.
  10. Install the application into a production portal with access to the features that are required by the integration.
    • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
    • Navigate to the copied link in your browser. Select a standard account in which to install the application.
    • Click Connect app. You can close the resulting tab.

Using a Private App

To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

You can generate a private application token by following the steps below:

  1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
  2. In the left sidebar menu, navigate to Integrations > Private Apps.
  3. Click Create private app.
  4. On the Basic Info tab, configure the details of your application (name, logo, and description).
  5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
  6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
  7. After you are done configuring your application, click Create app in the top right.
  8. Review the info about your application's access token, click Continue creating, and then Show token.
  9. Click Copy to copy the private application token.

To connect, set PrivateAppToken to the private application token you retrieved.

Connect and Transfer

To get started, add the code sample to a new project. You can execute the following command to save all tables without displaying them:

DO C:\Temp\sqldump.prg WITH "CData HubDB Source", "TESTDB", .f.

Below is the process that the program follows:

  1. Create a new FoxPro database.
  2. Open a connection to HubDB data with the line below:

    m.hSQLconnection = SQLCONNECT(m.cODBCDSN)
    
  3. If the connection was successful, you can now retrieve the list of tables using the SQLTABLES function. The code below saves the list of tables in sys_tables.dbf:

    WAIT WINDOW "Fetching tables for data source '" + m.cODBCDSN + "'..." NOWAIT NOCLEAR
    m.nSQLTABLES = SQLTABLES(m.hSQLconnection)
    
    IF lUseDistinctConnections
     WAIT WINDOW "Closing ODBC Connection for data source '" + m.cODBCDSN + "'..." NOWAIT NOCLEAR
     SQLDISCONNECT(m.hSQLconnection)
     m.hSQLconnection = 0 * SQLCONNECT needs to be called again
    ENDIF
    
    IF m.nSQLTABLES > 0
     * create local table containing list of tables in db
     COPY TO (m.cImportData + "sys_tables")
     USE
    
     * convert each table to DBF
     USE (m.cImportData + "sys_tables")
     ALTER TABLE DBF("sys_tables") ;
     ADD COLUMN records i ;
     ADD COLUMN dbfname m
    
  4. Scan over each table, saving it to a DBF file. The function ODBCtoDBF stores the table in a DBF file and then opens a grid if the lBrowse parameter is set to true:
    FUNCTION ODBCtoDBF (cTableName as String, cTableType as String, lBrowse as Logical, lhSQLConnection as Integer)
    
     WAIT WINDOW ;
     "Converting " + m.cTableType + ' "' + m.cTableName + '" to DBF...' ;
     NOWAIT NOCLEAR
    
     ACTIVATE SCREEN
    
     * strip characters incompatible with FoxPro out of the name of the DBF file
     m.cTableAlias		= ""
     m.nTableNameLen		= LEN(m.cTableName)
     m.nTableNameStart	= 1
     
     FOR m.nTableNameStart = 1 TO m.nTableNameLen
     m.cCharacter = SUBSTR(m.cTableName, m.nTableNameStart, 1)	
     IF !ISALPHA(m.cCharacter) .and. (m.nTableNameStart = 1 .or. !ISDIGIT(m.cCharacter))
     m.cTableAlias = m.cTableAlias + "_"
     ELSE
     m.cTableAlias = m.cTableAlias + m.cCharacter
     ENDIF
     ENDFOR
    
     m.cFromTable = m.cTableName
     m.cTempViewAlias	= m.cTableType + "_" + m.cTableAlias
    
     LOCAL loException as Exception
     LOCAL lnResultSets
     
     TRY
     * run query
     m.lnResultSets = SQLEXEC(m.lhSQLConnection, ;
     "SELECT * FROM " + m.cFromTable, ;
     m.cTempViewAlias, ;
     aSQLResult)
    	 
     IF m.lnResultSets#1
     SET STEP ON
     ENDIF
    	
     ACTIVATE SCREEN
    
     CATCH TO m.loException
     ACTIVATE SCREEN
     ? "Error opening " + m.cTempViewAlias + ":"
     ? m.loException.Message
     ? m.loException.Details
     ENDTRY
    
     IF !USED(m.cTempViewAlias)
     RETURN
     ENDIF
    
     * copy records from view cursor to disk
     SELECT * FROM (m.cTempViewAlias) ;
     INTO TABLE (m.cImportData + m.cTableAlias)
    
     IF USED(m.cTableAlias)
    
     ACTIVATE SCREEN
    
     FLUSH	&& flush the buffer to write the data to disk
    
     IF m.lBrowse
     * pop the table up on screen
     SELECT (m.cTableAlias)
     BROWSE NORMAL NOMODIFY NOWAIT
     ACTIVATE SCREEN
     ELSE
     * close on-disk table for now
     USE IN (m.cTableAlias)
     ACTIVATE SCREEN
     ENDIF
     ENDIF
    
     IF USED(m.cTempViewAlias)
     USE IN &cTempViewAlias && close SQL view
     ACTIVATE SCREEN
     ENDIF
    
     WAIT CLEAR
    
    ENDFUNC
    
  5. You can now save tables of HubDB data as DBF files.

Below is the full code, in FoxPro 9 syntax:

PARAMETERS cODBCDSN, cDatabaseName, lBrowseAfterConvert

*	cODBCDSN				The ODBC data source name, used for the name of the folder where the DBF tables are stored.
*	cDatabaseName			The name of the FoxPro database to use. This database is created if it does not exist. The default is DATABASE_NAME.
*								
*	lBrowseAfterConvert		If ".t." display each table with the BROWSE command after importing it. If ".f." close each table before moving on to the next one.

#define		ODBC_DATASOURCE		"DataSourceName"
#define		DATABASE_NAME		"odbcdata"

m.m_tpath = ".\" && root directory for data

ON ERROR
SET SAFETY OFF

IF VARTYPE(m.cODBCDSN)#"C" .or. EMPTY(m.cODBCDSN)
 m.cODBCDSN = ODBC_DATASOURCE
ENDIF
IF VARTYPE(m.cDatabaseName)#"C" .or. EMPTY(m.cDatabaseName)
 m.cDatabaseName = DATABASE_NAME
ENDIF

m.cImportData = m.cODBCDSN + "\"

CLOSE TABLES ALL
CLOSE DATABASES ALL

IF !DIRECTORY(m.cImportData)
	MKDIR (m.cImportData)
ENDIF

CREATE DATABASE (m.cDatabaseName)
CREATE CONNECTION (m.cDatabaseName) DATASOURCE (m.cODBCDSN) DATABASE (m.cDatabaseName)

WAIT WINDOW "Opening ODBC Connection for data source '" + m.cODBCDSN + "'..." NOWAIT NOCLEAR
m.hSQLconnection = SQLCONNECT(m.cODBCDSN)

IF m.hSQLconnection > 0
 * Connection successful; get list of tables
 WAIT WINDOW "Fetching tables for data source '" + m.cODBCDSN + "'..." NOWAIT NOCLEAR
 m.nSQLTABLES = SQLTABLES(m.hSQLconnection)

 IF m.nSQLTABLES > 0
 * Create local table containing list of tables in db
 COPY TO (m.cImportData + "sys_tables")
 USE

 * Convert each table to DBF
 USE (m.cImportData + "sys_tables")
 ALTER TABLE DBF("sys_tables") ;
 ADD COLUMN records	i ;
 ADD COLUMN dbfname	m

 SCAN	
 m.cCurrentTable	= TRIM(sys_tables.table_name)
 m.cCurrentTableType	= TRIM(sys_tables.table_type) && Valid values are "SYSTEMTABLE", "TABLE", and "VIEW".
 IF m.cCurrentTableType = "TABLE" or m.cCurrentTableType = "VIEW"

 ODBCtoDBF(m.cCurrentTable, m.cCurrentTableType, m.lBrowseAfterConvert, m.hSQLConnection)
 ELSE
 ACTIVATE SCREEN
 ? "ERROR:", m.cCurrentTable, "Couldn't open ODBC connection."
 =MESSAGEBOX("couldn't open data source " + m.cODBCDSN + " for table " + m.cCurrentTable + ".")
 ENDIF

 ENDSCAN
 BROWSE NORMAL NOWAIT

 ELSE
 =MESSAGEBOX("No tables found in data source " + m.cODBCDSN + ".")
 SET STEP ON
 ENDIF
 
 SQLDISCONNECT(m.hSQLconnection)
 
ELSE
 =MESSAGEBOX("Could not open data source " + m.cODBCDSN + ".")
 SET STEP ON
ENDIF

FUNCTION ODBCtoDBF (cTableName as String, cTableType as String, lBrowse as Logical, lhSQLConnection as Integer)

 WAIT WINDOW ;
 "Converting " + m.cTableType + ' "' + m.cTableName + '" to DBF...' ;
 NOWAIT NOCLEAR

 ACTIVATE SCREEN

 * Strip characters incompatible with FoxPro out of the name of the DBF file
 m.cTableAlias		= ""
 m.nTableNameLen		= LEN(m.cTableName)
 m.nTableNameStart	= 1
 
 FOR m.nTableNameStart = 1 TO m.nTableNameLen
 m.cCharacter = SUBSTR(m.cTableName, m.nTableNameStart, 1)	
 IF !ISALPHA(m.cCharacter) .and. (m.nTableNameStart = 1 .or. !ISDIGIT(m.cCharacter))
 m.cTableAlias = m.cTableAlias + "_"
 ELSE
 m.cTableAlias = m.cTableAlias + m.cCharacter
 ENDIF
 ENDFOR

 m.cFromTable = m.cTableName
 m.cTempViewAlias	= m.cTableType + "_" + m.cTableAlias

 LOCAL loException as Exception
 LOCAL lnResultSets
 
 TRY
 * Run query
 m.lnResultSets = SQLEXEC(m.lhSQLConnection, ;
 "SELECT * FROM " + m.cFromTable, ;
 m.cTempViewAlias, ;
 aSQLResult)
	 
 IF m.lnResultSets#1
 SET STEP ON
 ENDIF
	
 ACTIVATE SCREEN

 CATCH TO m.loException
 ACTIVATE SCREEN
 ? "Error opening " + m.cTempViewAlias + ":"
 ? m.loException.Message
 ? m.loException.Details
 ENDTRY

 IF !USED(m.cTempViewAlias)
 RETURN
 ENDIF

 * Copy records from view cursor to disk
 SELECT * FROM (m.cTempViewAlias) ;
 INTO TABLE (m.cImportData + m.cTableAlias)

 IF USED(m.cTableAlias)

 ACTIVATE SCREEN

 FLUSH	&& Flush the buffer to write the data to disk

 IF m.lBrowse
 * Display the table on screen
 SELECT (m.cTableAlias)
 BROWSE NORMAL NOMODIFY NOWAIT
 ACTIVATE SCREEN
 ELSE
 * Close on-disk table
 USE IN (m.cTableAlias)
 ACTIVATE SCREEN
 ENDIF
 ENDIF

 IF USED(m.cTempViewAlias)
 USE IN &cTempViewAlias && Close SQL view
 ACTIVATE SCREEN
 ENDIF

 WAIT CLEAR

ENDFUNC

Ready to get started?

Download a free trial of the HubDB ODBC Driver to get started:

 Download Now

Learn more:

👁 HubDB Icon
HubDB ODBC Driver

The HubDB ODBC Driver is a powerful tool that allows you to connect with live data from HubDB, directly from any applications that support ODBC connectivity.

Access HubDB data like you would a database - read, write, and update HubDB 0, etc. through a standard ODBC Driver interface.