Feedback
Did this article resolve your question/issue?

   

Article

DataServer OpenEdge to SQL utility fails to create tables with the correct name

Information

 
TitleDataServer OpenEdge to SQL utility fails to create tables with the correct name
URL Namedataserver-openedge-to-sql-utility-fails-to-create-tables-with-the-correct-name
Article Number000192813
EnvironmentProduct: OpenEdge
Version: 11.6
OS: Windows
Other: DataServer
Question/Problem Description
DataServer OpenEdge to SQL utility fails to create tables with the correct name.

The first table in the foreign database is created with the name "Z".

The second and subsequent tables are created in the foreign database starts with a number.
Steps to Reproduce
Clarifying Information
The table definition contains the string: QUALIFIER ""
Error Message
Defect/Enhancement NumberPSC00349635
Cause
Defect PSC00349635
Resolution
None at this time.
Workaround
Remove from the table definition in the .df the line with the string: QUALIFIER ""
Notes
Last Modified Date8/4/2016 11:31 PM
Attachment 
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.