Feedback
Did this article resolve your question/issue?

   

Article

For Salesforce ODBC driver 7.1, how to refresh the local database configuration files in an application?

Information

 
TitleFor Salesforce ODBC driver 7.1, how to refresh the local database configuration files in an application?
URL Namefor-salesforce-odbc-driver-7-1-how-to-refresh-the-local-database-configuration-files-from-an-application
Article Number000119515
EnvironmentProduct: Connect64 XE for ODBC Salesforce driver
Version: 7.1
OS: Windows
Database: Salesforce
Application: All supported applications
Question/Problem Description
When a client application creates new tables or new coulmns for an existing table, catalog function calls (like SQLColumns, SQLTables)  does not return the new changes.
 Are there any function calls that can be used in the client application to refresh the local database configuration files so that catalog function calls will return the new changes?
 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Use REFRESH SCHEMA SQL Extension in the application  to refresh the local database configuration files.

Here is the Salesforce ODBC documentation link which describes the above:
https://media.datadirect.com/download/docs/odbc/allodbc/index.html#page/odbc%2Frefresh-schema-(ext).html%23wwID0EH2B6
Workaround
Notes
Last Modified Date1/3/2020 12:32 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.