Services Partners Company
Knowledge Base


Article

Reserved error -7748 linking OE table in MS Access

« Go Back

Information

 
EnvironmentProduct: OpenEdge
Version: 10.1x, 10.2x
OS: Windows
Other: MS Access versions 2003, 2007, and 2010
Question/Problem Description
Reserved error -7748 when attempting to link a OpenEdge 10.x database table in Microsoft Access

Reserved error (-7748): there is no message for this error

Error in ODBC trace file:
DIAG [01004] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]String data, right truncated. Error in column 10. (0)

Problem occurs when using the 5.1 DataDirect driver shipped with 10.1A.

Problem occurs when using the 5.1 DataDirect driver shipped with 10.1B.

Problem occurs when using the 5.1 DataDirect driver shipped with 10.2B.
Steps to Reproduce
Clarifying Information
Problem does not occur with the 4.2 DataDirect driver shipped with 10.0B
Error MessageReserved error (-7748): there is no message for this error

DIAG [01004] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver]String data, right truncated. Error in column 10. (0)
Defect/Enhancement Number
Cause
The problem is caused by an issue within Microsoft Access, not the DataDirect driver.

Microsoft Access 2000 calls SQLStatisticsW and SQLGetData for column number 10. Microsoft Access only asks for the data as a two-byte SQL_C_WCHAR, which is insufficient buffer to store the UCS2 character and the null terminator. Thus, the driver returns a warning, "01004 Data truncated", and returns a null character to Microsoft Access. Microsoft Access then passes error -7748.  
Resolution
None at this time.
Workaround
WARNING - You should always make a backup of the Registry before making any changes.

To resolve this error, set WorkArounds2=8192 for the affected data source.  This can be done by using the Registry Editor (RegEdit).

1.  Run RegEdit

2. Locate the ODBC DSN in the Registry:

For a USER Data Source, go to HKEY_CURRENT_USER -> Software -> ODBC -> ODBC.INI -> YourDataSourceName

For a SYSTEM Data Source, go to HKEY_LOCAL_MACHINE -> Software -> ODBC -> ODBC.INI -> YourDataSourceName

For 32-bit applications (ODBC drivers) on 64-bit Windows, (MACHINE) Data Source, go to

HKEY_LOCAL_MACHINE -> Software -> Wow6432Node -> ODBC -> ODBC.INI -> YourDataSourceName

3.  Click on the folder for your data source; from the menu choose:
Edit -> New -> String Value

4.  Set the name of the new string value to be WorkArounds2

5.  Double click on WorkArounds2 in the right hand panel; this will bring up a dialog box with a data value field

6.  Change the data value to 8192 (The string value that must be added to Windows XP SP2 and Progress 10.1A02 is WorkArounds2=40960)

7.  Click OK

8.  Close RegEdit

PCs running Windows 95 and 98 need to be rebooted for this setting to take effect

9. NOTE: When using a FILE DSN, simply open the (text) FILE DSN with your favorite text editor, add the following string to its contents (without quotes and using the appropriate (integer) value for <nnnnn>: "WorkArounds2=<nnnnn>". Save the file.

Notes
Attachment 
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.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful.



Characters Remaining: 255