PowerBuilder problem

Hello,

I am trying to modify my MS SQL 2005 database by PowerDesigner model using PowerDesigner built-in Modify feature.

PD however seems to have problems reverse engineering the database.

I get tons of errors like this:
Reverse engineering tables...
Table _MyTable
Unable to list the columns.
[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.
SQLSTATE = 37000

It also seems that it generates incompatible SQL code when modifying the database. E.g. (Parentheses after nonclustered violates syntax)...

create table _H_IpNetworkToVlanNetwork (
ipNetAddress bigint null,
vpnNetId int null default 0,
vlanId int null,
_ChangeDate datetime null,
_ChangeType int null,
constraint PK__H_IPNETWORKTOVLANNETWORK primary key nonclustered ()
)
go

What may be wrong? Do I have badly configured PowerBuilder? Or maybe badly configured ODBC data source?

Thanks for any help.

I have PowerBuilder 12.1 and MS SQL 2005Sounds like a PB problem. So tell me again why you dropped this in the SQL Server forum?|||Oh, ok sorry, where should I put this then? Thanks|||It is partially a Power Designer problem, so knowing how it works helps, but the problem appears in SQL Server (in other words SQL 2005 is the first product to complain).

The problem is that you once had a primary key defined for the table, then you removed the PK definition. This leaves Power Designer a bit confused, since it never seems to figure out that there isn't really a PK anymore. The fine folks at Sybase have a hot fix for this problem, and it is going to be addressed in a future service pack.

The work around is to either a) re-declare a PK so that Power Designer can work with the existing table, or b) re-create the table inside Power Designer without specifying a PK. More than 95% of the time you really want to have a Primary Key and simply undefined it by accident.

-PatP|||Hello Pat,

Thanks for your reply.

I however don't seem to have any problem with primary keys. They are set the same way in the designer as they are in database. Or maybe I understood you incorrectly.

Thanks|||The empty set of parentheses in the PRIMARY KEY clause of your posted SQL indicates that PowerDesigner does not have any Primary Key defined for the _H_IpNetworkToVlanNetwork table. This normally means that you once had a Primary Key defined, but that somehow it is no longer defined.

-PatP|||Ok, now I get it. It was actually a different problem that I thought you were talking about. I think now all my problems are resolved, thanks for helping :-)

The problem was that I had wrong DMBS selected and there were some incompatibilities.

PowerBuilder connect to Access(get an error SQLSTATE = 01S01 )

I am trying to connect Microsoft Access Database from PowerBuilder(ODBC),
when execute a select clause, get an error SQLSTATE = 01S01(Row errors), bu
t
trying open the database from Microsoft Access 2000 tools , the row is very
good. I am puzzled this error. Someone help me to this problem, pleaseHi
This is a SQL Server newsgroup a better place to post this would be a
powerbuilder or Access newsgroup. Searching google for 01S01 returned quite
a
few hits
http://tinyurl.com/79ru9
this one looked promising
http://tinyurl.com/cr6u7
and indicates that is pssibly masking the real error which in this case the
truncation of a string.
John
"guo-feng lui via webservertalk.com" wrote:

> I am trying to connect Microsoft Access Database from PowerBuilder(ODBC
),
> when execute a select clause, get an error SQLSTATE = 01S01(Row errors),
but
> trying open the database from Microsoft Access 2000 tools , the row is ver
y
> good. I am puzzled this error. Someone help me to this problem, please
>sql

Powerbuilder 10.5.1.6662 Connection to SQL Server 2005

Recently, an application has been migrated from Powerbuilder 9.0 to
Powerbuilder 10.5 Build 6662. This application uses an .INI file
located in the Windows folder. The connection to the database, which
has also been migrated from SQL 2000 to SQL 2005 is as follows:
[database]
DBMS=OLE DB
Database=db_lps_prd_01
ServerName=USDANS402
dbParm=Connectstring=PROVIDER='SQLOLEDB',DATASOURC E='USDANS402',INTEGRATEDSX
ECURITY='SSPI',DATABASE=db_lps_prd_01
yet when a user tries to connect to this database, using an embedded
DECLARE and EXECUTE statement, and has access to other databases,
through Active Directory, the Powerbuilder application issues an
error: "you do not have the security credentials necessary to run the
application" Even if you fully qualify the procedure name SQL 2005
throw error 2812, which is equilavent to the application error. If
you remove the user from other databases, then the user can access
the
database in question. Now access to this database has 4 different
security levels in which users are assigned, and those security
levels
are Active Directory access accounts. The gist of it all seems to
be; between Powerbuilder 10.5.1 Build 6662 and SQL Server 2005, when
using the connectivity string defined in the .INI file, apparently
the
user is connecting to some other database trying to execute the
embedded procedure. Can anyone offer insight to this situation?
PowerBuilder? Really? I had not heard that there were any of those systems
still around. Good luck with that...
I think you're on the right track... check if the SQL Server has any links
established. Make sure the registered credentials are correct.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"dmmcgrue" <Donna.McGrue@.amgreetings.com> wrote in message
news:1186146671.268576.31950@.z24g2000prh.googlegro ups.com...
Recently, an application has been migrated from Powerbuilder 9.0 to
Powerbuilder 10.5 Build 6662. This application uses an .INI file
located in the Windows folder. The connection to the database, which
has also been migrated from SQL 2000 to SQL 2005 is as follows:
[database]
DBMS=OLE DB
Database=db_lps_prd_01
ServerName=USDANS402
dbParm=Connectstring=PROVIDER='SQLOLEDB',DATASOURC E='USDANS402',INTEGRATEDSX
ECURITY='SSPI',DATABASE=db_lps_prd_01
yet when a user tries to connect to this database, using an embedded
DECLARE and EXECUTE statement, and has access to other databases,
through Active Directory, the Powerbuilder application issues an
error: "you do not have the security credentials necessary to run the
application" Even if you fully qualify the procedure name SQL 2005
throw error 2812, which is equilavent to the application error. If
you remove the user from other databases, then the user can access
the
database in question. Now access to this database has 4 different
security levels in which users are assigned, and those security
levels
are Active Directory access accounts. The gist of it all seems to
be; between Powerbuilder 10.5.1 Build 6662 and SQL Server 2005, when
using the connectivity string defined in the .INI file, apparently
the
user is connecting to some other database trying to execute the
embedded procedure. Can anyone offer insight to this situation?

Powerbuilder 10.5.1.6662 Connection to SQL Server 2005

Recently, an application has been migrated from Powerbuilder 9.0 to
Powerbuilder 10.5 Build 6662. This application uses an .INI file
located in the Windows folder. The connection to the database, which
has also been migrated from SQL 2000 to SQL 2005 is as follows:
[database]
DBMS=3DOLE DB
Database=3Ddb_lps_prd_01
ServerName=3DUSDANS402
dbParm=3DConnectstring=3DPROVIDER=3D'SQL
OLEDB',DATASOURCE=3D'USDANS402',INT=
EGRATEDS=AD
ECURITY=3D'SSPI',DATABASE=3Ddb_lps_prd_0
1
yet when a user tries to connect to this database, using an embedded
DECLARE and EXECUTE statement, and has access to other databases,
through Active Directory, the Powerbuilder application issues an
error: "you do not have the security credentials necessary to run the
application" Even if you fully qualify the procedure name SQL 2005
throw error 2812, which is equilavent to the application error. If
you remove the user from other databases, then the user can access
the
database in question. Now access to this database has 4 different
security levels in which users are assigned, and those security
levels
are Active Directory access accounts. The gist of it all seems to
be; between Powerbuilder 10.5.1 Build 6662 and SQL Server 2005, when
using the connectivity string defined in the .INI file, apparently
the
user is connecting to some other database trying to execute the
embedded procedure. Can anyone offer insight to this situation?PowerBuilder? Really? I had not heard that there were any of those systems
still around. Good luck with that...
I think you're on the right track... check if the SQL Server has any links
established. Make sure the registered credentials are correct.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"dmmcgrue" <Donna.McGrue@.amgreetings.com> wrote in message
news:1186146671.268576.31950@.z24g2000prh.googlegroups.com...
Recently, an application has been migrated from Powerbuilder 9.0 to
Powerbuilder 10.5 Build 6662. This application uses an .INI file
located in the Windows folder. The connection to the database, which
has also been migrated from SQL 2000 to SQL 2005 is as follows:
[database]
DBMS=OLE DB
Database=db_lps_prd_01
ServerName=USDANS402
dbParm=Connectstring=PROVIDER='SQLOLEDB'
,DATASOURCE='USDANS402',INTEGRATEDS_
ECURITY='SSPI',DATABASE=db_lps_prd_01
yet when a user tries to connect to this database, using an embedded
DECLARE and EXECUTE statement, and has access to other databases,
through Active Directory, the Powerbuilder application issues an
error: "you do not have the security credentials necessary to run the
application" Even if you fully qualify the procedure name SQL 2005
throw error 2812, which is equilavent to the application error. If
you remove the user from other databases, then the user can access
the
database in question. Now access to this database has 4 different
security levels in which users are assigned, and those security
levels
are Active Directory access accounts. The gist of it all seems to
be; between Powerbuilder 10.5.1 Build 6662 and SQL Server 2005, when
using the connectivity string defined in the .INI file, apparently
the
user is connecting to some other database trying to execute the
embedded procedure. Can anyone offer insight to this situation?

Powerbuilder : how to get height value

how can i get height value on autosize column but not RowHeight() 'couse RowHeight() return a row height value not a column height value.
i already try use dw_report.object.MyColumn.height , but its retrun a height value before it resize...
pleasee help
sory my english not goodWrong Thread
Please Delete And Post In Correct Thread

Power Builder 6.5 Software

I need to know if the 6.5 version of Powerbuilder is
compatible with Windows XP.
If not please indicate the particular version and/or
alternative that is compatible with Windows XP.This is more of a Power Builder issue, you'll probably get a better response
in a Power Builder newsgroup!
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"bjbudgett@.kcc.usda.gov" <anonymous@.discussions.microsoft.com> wrote in
message news:104401c3b43c$0304f5c0$a501280a@.phx.gbl...
I need to know if the 6.5 version of Powerbuilder is
compatible with Windows XP.
If not please indicate the particular version and/or
alternative that is compatible with Windows XP.