使用 SQL Server DB 将 PB7 迁移到 10.5
我在 SQL Server DB 上将 PB7 迁移到 PB10.5。系统给我这条消息:
“您当前的系统不支持 DBMS MSS Microsoft SQL Server 6.x 安装”
我更改了数据库连接设置: PB7 中使用的旧连接:
- DBMS = MSS Microsoft SQL Server 6.x
- Database = databaseName
- ServerName = serverName
- LogId = LogId
- AutoCommit = 1
- DBParm = ""
- UserId = userid
- DatabasePassword =
- LogPassword=password
- Lock=
- Prompt=0
PB10.5 中的此操作:
- DBMS =SNC SQL Native Client(OLE DB)
- 数据库 = 数据库名称
- 服务器名称 = 服务器名称
- LogId = LogId
- AutoCommit = 0
- DBParm = "
- Database='databaseName'
- TrimSpaces=1"
- UserId=userid
- DatabasePassword=
- LogPassword=password
- Lock=
- Prompt=0
系统运行时没有以前的错误消息,但是当检索数据窗口中任何旧存储的阿拉伯语数据时,它似乎不可读
乌云密布
I migrated PB7 to PB10.5 on SQL server DB. The system gives me this message:
"DBMS MSS Microsoft SQL Server 6.x is not supported in your current
installation"
I changed the database connection settings from:
Old connect used in PB7:
- DBMS = MSS Microsoft SQL Server 6.x
- Database = databaseName
- ServerName = serverName
- LogId = LogId
- AutoCommit = 1
- DBParm = ""
- UserId = userid
- DatabasePassword =
- LogPassword=password
- Lock=
- Prompt=0
To this in PB10.5:
- DBMS =SNC SQL Native Client(OLE DB)
- Database =databaseName
- ServerName =serverName
- LogId =LogId
- AutoCommit = 0
- DBParm = "
- Database='databaseName'
- TrimSpaces=1"
- UserId=userid
- DatabasePassword=
- LogPassword=password
- Lock=
- Prompt=0
The system run without previous error message,but when retrieve any old stored arabic data in datawindows it seem unreadable like
ÚãáíÇÊ ÇÎÑì
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我不敢相信这个问题被忽视了——对此感到抱歉。从旧版本的 PowerBuilder 迁移到 PowerBuilder 版本 10 及更高版本时,这是一个常见问题。好消息,修复起来非常容易,只是可能会很耗时,具体取决于需要修复的地方有多少。
我已经写了一篇关于该主题的博客文章,或者只是 duckduckgo 迁移 PowerBuilder Unicode 问题。
转换 ANSI 和 Unicode 字符串以将 PowerBuilder 迁移到版本 10 及更高版本< /a>
以下是转换过程的摘要:
将数据转换为 ANSI
将通过文件读取的数据转换为 ANSI
I can't believe this question got overlooked -- sorry about that. It is a common question when migrating from older versions of PowerBuilder to PowerBuilder version 10 and higher. Good news, very easy to fix just can be time consuming depending on how many places you need to fix.
I've already written a blog article on the subject or just duckduckgo migrating PowerBuilder Unicode issues.
Converting ANSI and Unicode Strings for PowerBuilder Migrations to Version 10 and Higher
Here is a summary of the conversion process:
Convert data to ANSI
Convert data read via file to ANSI