OpenEDGE SQL ODBC显示的列大小与本机ABL不同
我正在使用Progress OpenEDGE ODBC驱动程序（PEOE27.DLL V07.16.0175）将数据推入OpenEDGE数据库。我的情况是，用户放入54个字符长的字符串值，在更新过程中被拒绝，因为它超过了定义的列大小为50，如下图中的第二张图中可见。
然后，传统系统管理员向我发送了一个屏幕截图，显示就ABL而言，同一表中同一列的宽度为200个字符。 （请参阅第一个图像）
有人有解释吗？ （除了ABL和OpenEDGE ODBC外，一个可怕的平台...：P）
I'm using the Progress OpenEdge ODBC driver (peoe27.dll v07.16.0175) to push data into an OpenEdge database. I had a situation where a user put in a string value that was 54 characters long, which got rejected during the update because it exceeded the defined column size of 50, as visible in the second image below.
The legacy system admin then sent me a screen shot showing that, as far as ABL was concerned, the width on that same column in that same table was 200 characters. (see the first image)
Anyone have an explanation? (Other than that ABL and OpenEdge ODBC are a terrible platform... :P )
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
传统数据库管理员找到了答案。似乎有一些方法可以更改OpenEDGE表的架构，该架构不会以外部请求者可以看到的方式“发布”。
显然，DLC中有一个“ DBTool实用程序”可以扫描并解决此问题。他研究了它，做到了这一点。
如果您正在使用类似的问题阅读此书，而上述则不足以使您过去，那么PM，我将获得更多详细信息。
Legacy DB admin found the answer. Seems there are ways to change the schema of an OpenEdge table that does not get "published" in such a way that external requesters can see it.
Apparently there is a "dbtool utility in dlc" that can scan and fix this. He researched it and did just that.
If you're reading this with similar issues and the above isn't enough to get you past, PM and I'll get more details.