PB 7.0 Client Cursor and MS SQL Server 7.0

We are in the process of migrating from MS SQL 6.5 to MS SQL 7.0 and are
running with PB 7.0 build 5031.  Our PB application uses a cursor which
works fine with MS SQL 6.5 but we are getting the following error with MS
SQL 7.0 when we open the cursor:
        SQLCODE = -1
        SQLDBCODE = 999
        SQLERRTEXT= "34000[Microsoft][ODBC SQL Server Driver] Invalid cursor
name"

Is there a different database connection setting, different way to set up
transaction object, different setting on ODBC connection, or something else
that we should be doing or looking at when we go to MS SQL 7.0 when dealing
with client cursors? Any assistance or advice would be greatly appreciated.
Thank-you!

Here's the DECLARE and OPEN:

    DECLARE action_cursor CURSOR FOR
 SELECT a.claimant_nmidno, a.di_dino, a.action_flup_class_id,
a.action_timestamp,
        a.action_flup_per_id, a.action_requestor_per_id, x.claim_hna_clno1
  FROM action a, disability d, disability_xref x
  WHERE a.claimant_nmidno = d.claimant_nmidno AND a.di_dino = d.di_dino AND
    a.claimant_nmidno = x.claimant_nmidno AND a.di_dino = x.di_dino AND
    a.action_cmpl_date IS NULL AND a.action_flup_date IS NOT NULL AND
    a.action_flup_ovrd_per_id IS NULL AND
    d.di_flup_rpt_ind != 'N'
     using gtr_cursor;

//Open the cursor
OPEN action_cursor;




0
Laurinda
3/27/2001 8:58:50 PM
sybase.powerbuilder.database 9855 articles. 2 followers. Follow

3 Replies
801 Views

Similar Articles

[PageSpeed] 39

I don't know if this will fix your problem, but build 5031 is some 2 years
old and very buggy, I'd strongly suggest upgrading to a more recent version.
If you don't rely on DB-OLE objects in datawindows (which are broken in most
flavours of 7.0.2) I'd go for C3 (build 8046).
S.

--
Simon Caldwell
Get Real Systems Ltd
Holtby Manor, Stamford Bridge Road, York, YO19 5LL
Tel 01904 481999 Fax 01904 481666
Visit us at www.getrealsystems.com

Specialists in e-Procurement and supply chain technology


"Laurinda Zoufaly" <L.Zoufaly@monarchlife.com> wrote in message
news:D$WC3NwtAHA.208@forums.sybase.com...
> We are in the process of migrating from MS SQL 6.5 to MS SQL 7.0 and are
> running with PB 7.0 build 5031.  Our PB application uses a cursor which
> works fine with MS SQL 6.5 but we are getting the following error with MS
> SQL 7.0 when we open the cursor:
>         SQLCODE = -1
>         SQLDBCODE = 999
>         SQLERRTEXT= "34000[Microsoft][ODBC SQL Server Driver] Invalid
cursor
> name"
>
> Is there a different database connection setting, different way to set up
> transaction object, different setting on ODBC connection, or something
else
> that we should be doing or looking at when we go to MS SQL 7.0 when
dealing
> with client cursors? Any assistance or advice would be greatly
appreciated.
> Thank-you!
>
> Here's the DECLARE and OPEN:
>
>     DECLARE action_cursor CURSOR FOR
>  SELECT a.claimant_nmidno, a.di_dino, a.action_flup_class_id,
> a.action_timestamp,
>         a.action_flup_per_id, a.action_requestor_per_id, x.claim_hna_clno1
>   FROM action a, disability d, disability_xref x
>   WHERE a.claimant_nmidno = d.claimant_nmidno AND a.di_dino = d.di_dino
AND
>     a.claimant_nmidno = x.claimant_nmidno AND a.di_dino = x.di_dino AND
>     a.action_cmpl_date IS NULL AND a.action_flup_date IS NOT NULL AND
>     a.action_flup_ovrd_per_id IS NULL AND
>     d.di_flup_rpt_ind != 'N'
>      using gtr_cursor;
>
> file://Open the cursor
> OPEN action_cursor;
>
>
>
>


0
Simon
3/28/2001 8:10:40 AM
I have a similar situation in which I can connect to MSSQL 7 using ODBC, but
whenever I issue an embedded SQL statement, I get an error something like
"...invalid object <tablename>...", when I know the table is valid.

If you find a solution, please post it.

Tim
"Laurinda Zoufaly" <L.Zoufaly@monarchlife.com> wrote in message
news:D$WC3NwtAHA.208@forums.sybase.com...
> We are in the process of migrating from MS SQL 6.5 to MS SQL 7.0 and are
> running with PB 7.0 build 5031.  Our PB application uses a cursor which
> works fine with MS SQL 6.5 but we are getting the following error with MS
> SQL 7.0 when we open the cursor:
>         SQLCODE = -1
>         SQLDBCODE = 999
>         SQLERRTEXT= "34000[Microsoft][ODBC SQL Server Driver] Invalid
cursor
> name"
>
> Is there a different database connection setting, different way to set up
> transaction object, different setting on ODBC connection, or something
else
> that we should be doing or looking at when we go to MS SQL 7.0 when
dealing
> with client cursors? Any assistance or advice would be greatly
appreciated.
> Thank-you!
>
> Here's the DECLARE and OPEN:
>
>     DECLARE action_cursor CURSOR FOR
>  SELECT a.claimant_nmidno, a.di_dino, a.action_flup_class_id,
> a.action_timestamp,
>         a.action_flup_per_id, a.action_requestor_per_id, x.claim_hna_clno1
>   FROM action a, disability d, disability_xref x
>   WHERE a.claimant_nmidno = d.claimant_nmidno AND a.di_dino = d.di_dino
AND
>     a.claimant_nmidno = x.claimant_nmidno AND a.di_dino = x.di_dino AND
>     a.action_cmpl_date IS NULL AND a.action_flup_date IS NOT NULL AND
>     a.action_flup_ovrd_per_id IS NULL AND
>     d.di_flup_rpt_ind != 'N'
>      using gtr_cursor;
>
> file://Open the cursor
> OPEN action_cursor;
>
>
>
>


0
Tim
4/5/2001 2:51:30 PM
This is not the old Sybase problem, general connection therefore the table
owner is also required?
i.e.
SELECT table.*
FROM "dbo"."<dbo_owned_table>" table

Cheers, Paul

"Tim" <nobody@nowhere.com> wrote in message
news:$8LqgKevAHA.259@forums.sybase.com...
> I have a similar situation in which I can connect to MSSQL 7 using ODBC,
but
> whenever I issue an embedded SQL statement, I get an error something like
> "...invalid object <tablename>...", when I know the table is valid.
>
> If you find a solution, please post it.
>
> Tim
> "Laurinda Zoufaly" <L.Zoufaly@monarchlife.com> wrote in message
> news:D$WC3NwtAHA.208@forums.sybase.com...
> > We are in the process of migrating from MS SQL 6.5 to MS SQL 7.0 and are
> > running with PB 7.0 build 5031.  Our PB application uses a cursor which
> > works fine with MS SQL 6.5 but we are getting the following error with
MS
> > SQL 7.0 when we open the cursor:
> >         SQLCODE = -1
> >         SQLDBCODE = 999
> >         SQLERRTEXT= "34000[Microsoft][ODBC SQL Server Driver] Invalid
> cursor
> > name"
> >
> > Is there a different database connection setting, different way to set
up
> > transaction object, different setting on ODBC connection, or something
> else
> > that we should be doing or looking at when we go to MS SQL 7.0 when
> dealing
> > with client cursors? Any assistance or advice would be greatly
> appreciated.
> > Thank-you!
> >
> > Here's the DECLARE and OPEN:
> >
> >     DECLARE action_cursor CURSOR FOR
> >  SELECT a.claimant_nmidno, a.di_dino, a.action_flup_class_id,
> > a.action_timestamp,
> >         a.action_flup_per_id, a.action_requestor_per_id,
x.claim_hna_clno1
> >   FROM action a, disability d, disability_xref x
> >   WHERE a.claimant_nmidno = d.claimant_nmidno AND a.di_dino = d.di_dino
> AND
> >     a.claimant_nmidno = x.claimant_nmidno AND a.di_dino = x.di_dino AND
> >     a.action_cmpl_date IS NULL AND a.action_flup_date IS NOT NULL AND
> >     a.action_flup_ovrd_per_id IS NULL AND
> >     d.di_flup_rpt_ind != 'N'
> >      using gtr_cursor;
> >
> > file://Open the cursor
> > OPEN action_cursor;
> >
> >
> >
> >
>
>


0
Paul
4/5/2001 10:53:29 PM
Reply:

Similar Artilces:

Connection of PB 6.0 to SQL Server 7.0 & Version B/W PB 6.0 and PB 7.0
Can anyone tell me about connecting PB 6.0 to SQL Server 7.0. Please remember we are not planning to upgrade both software. When I was trying to connect PB 6.0 to SQL Server 7.0, error occurred " SQLSTAT 1003". OS=NT 4.0 Server PB=6.0 Enterprise Edition SQL SERVER=7.0 Corporate Edition I also want to know the versions between PB 6.0 to PB 7.0 If your are using the ODBC, which I assume you are, include Disablebind=1 in your DBParm. If your deployment environment is also NT, you will have to turn SQLSPY=1 using PFC services. Autocommit=FALSE and SetTransObject() ra...

PROBLEM with PB 7.0.3 AND SQL SERVER 7.0 USING SQL CURSOR
I am having a problem running a sql command with a cursor with Native drivers for MS sql Server 7.0.If i use ODBC or take out the order by clause in the statement it works fine By the way I am running powerbuilder 7.0.3 build 10009 The error code is : (Error 10008 (DB-Library) DB-Library Severity Level 9 Message Text ad token from SQL Server: Datastream processing out of synchronization) here a sample of the code DECLARE cur_Sec1 CURSOR FOR SELECT DISTINCT COL1,COL2 FROM TABLE1 WHERE COL1 = ??? ORDER BY COL1 ASC ; <<<<<<<<<<< ...

Help me about connecting PB 6.0 to SQL Server 7.0 & Versions B/W PB 6.0 and PB 7.0
Can anyone tell me about connecting PB 6.0 to SQL Server 7.0. Please remember we are not planning to upgrade both software. When I was trying to connect PB 6.0 to SQL Server 7.0, error occurred " SQLSTAT 1003". OS=NT 4.0 Server PB=6.0 Enterprise Edition SQL SERVER=7.0 Corporate Edition I also want to know the versions between PB 6.0 to PB 7.0 I don't believe this is going to be possible without at least upgrading to the latest maintenance release of 6.x. On Mon, 23 Aug 1999 00:59:56 -0700, in powersoft.public.powerbuilder.database Abdul Lateef <abdul_lat...

PB 7.0.2 and MS SQL Server 7.0
Hello everyone, I am running PB 7.0.2 (Build 8046) and I am trying to connect to MS SQL Server 7.0 database. I can connect to the database via ODBC with no problems, but when I attempt to use the MS SQL Client Software 7.0, I get an error "Could not connect to database." Is SQL Client Software v7.0 even supported with PB 7x or do I have to go to 6.0 of SQL Client? -- Thanks, Daryl L. Avery Development Technologies Consultant Software Spectrum, Inc. E-mail: Daryl.Avery@SoftwareSpectrum.com Website: SoftwareSpectrum.com Voice: (972) 864-5114 Fax: (972) 864-3292 ...

Problem with PB 7.0 And MS SQL Server 7.0 ODBC
I am having some problem using PowerBuilder 7.0 with MS SQL Server 7.0 and ODBC. Arguments to datawindows and nested SQL doesn't seem the work properly. The following is some lines from the ODBC trace-file: SELECT report.reportkey, report.reporttype, report.reportname FROM report WHERE exists (SELECT reportparam.reportkey FROM reportparam WHERE ( reportparam.reportkey = report.reportkey ) AND reportparam.paramtype = ? )) ORDER BY report.reportname VCHAR Length=4 ID=:as_paramtype *test* (10 MilliSeconds) Error 999 (rc -1) : SQLSTATE ...

PB 7.0 and MS-SQL Server 7.0 login problem
I am having a problem connecting my app to the MS SQL-Server database. I'm sure it's something obvious that I'm missing. From my computer, it connects just finewith no login box. When I try to connect from a different computer, a login window pops up with "Admin" as the log in name. The database should be using a trusted connection from a computer within the domain. The user on the computer is successfully logged into the (NT 4) domain. Any ideas what I am failing to do? Hi, You must provide a valid login id on the other PC you specified and this login must ...

PB 7.0 DataWindows and MS SQL Server 7.0 Stored Procedures
I'm having some problems with creating a datawindow from a stored procedure. I have migraited a PB 5.0.4 application to PB 7.0 with no difficulties. This app has datawindows that are running off of stored procs. But, when I try to create a new tabular datawindow fromscratch (I also tried this using a stored proc that is being used to power other datawindows) I get the following message: Cannot create DataWindow 'Data-conversion resulted in overflow' If any one knows what I am doing wrong I'd appreciate the help. BTW, I am connecting with the native MS SQL Ser...

PB 7.0 DataWindows and MS SQL Server 7.0 Stored Procedures
I'm having some problems with creating a datawindow from a stored procedure. I have migraited a PB 5.0.4 application to PB 7.0 with no difficulties. This app has datawindows that are running off of stored procs. But, when I try to create a new tabular datawindow fromscratch (I also tried this using a stored proc that is being used to power other datawindows) I get the following message: Cannot create DataWindow 'Data-conversion resulted in overflow' If any one knows what I am doing wrong I'd appreciate the help. BTW, I am connecting with the native MS SQL Serv...

Powerbuilder 5.0/7.0 and MS SQL 7.0 Performance issues
We recently converted our app from Powerbuilder 5.0 to PB 7.0 -- the app in PB 7.0 definitely runs slower on the client PC's than it did in PB 5.0. Now we are migrating the database from MS SQL 6.5 to 7.0 SP2. We successfully converted the databases in a testing environment, but now the app runs terribly slow! I don't think it's a hardware issue -- the test box is a Compaq 8500 quad Xeon 500 w/1GB Ram. We experimented running the app as a PB 5.0 app against MS SQL 7.0 and the problem is the same. When we execute SQL directly against the DB outside of PB, we see no perf...

PowerBuilder 7.0 & SQL Server 7.0
Hi: I've develop an application that connect to and MS SQL SERVER 7.0 database via ODBC. When i make the .exe file and run it in Win95 or Windows NT Workstation it works fine, but when i run it in a Win98 client the following error apears. SQLSTATE=22005 - "Invalid character value for cast specification." Any clues about this. The exe was build in PowerBuilder 7.0 over a Windows NT Workstation 4.0 Thanks in advance. Jorge, Try adding to the dbparm - CallEscape='No'. Here is an example: SQLCA.DBParm = "Connectstring='DSN=<your ...

PB 7.0 MS SQL 7.0 uniqueidentifier
Hello I have a problem with with uniqueidentifier column. I have table with one uniqueidentifier columne when I try to run select like this within database painter: select * from table_name; I have an error about using embeded SQL. The same SQL runned within aplication dosn't raise an errror but value from uniqueidentifier column is truncated. Help. (PB 7.0, MS SQL 7.0, OLE DB - SQLOLEDB) ...

PowerBuilder 7.0 & SQL Server 7.0
Hi: I've develop an application that connect to and MS SQL SERVER 7.0 database via ODBC. When i make the .exe file and run it in Win95 or Windows NT Workstation it works fine, but when i run it in a Win98 client the following error apears. SQLSTATE=22005 - "Invalid character value for cast specification." Any clues about this. The exe was build in PowerBuilder 7.0 over a Windows NT Workstation 4.0 Thanks in advance. Jorge, Try adding to the dbparm - CallEscape='No'. Here is an example: SQLCA.DBParm = "Connectstring='DSN=<your ...

Connect MS-SQL 7.0 in PowerBuilder 7.0
In PowerBuilder 6.5, I can connect MS-SQL 6.5 directly not using ODBC, but in PowerBuilder 7.0, how can I connect MS-SQL 7.0 directly ? Please post to the powersoft.public.powerbuilder newsgroups This is dedicated to PB issues when used within Jaguar Masun wrote: > In PowerBuilder 6.5, I can connect MS-SQL 6.5 directly not using ODBC, but > in PowerBuilder 7.0, how can I connect MS-SQL 7.0 directly ? ...

PB 7.0 MS SQL 7.0 Uniqueidentifier
Hello I have a problem with with uniqueidentifier column. I have table with one uniqueidentifier columne when I try to run select like this within database painter: select * from table_name; I have an error about using embeded SQL. The same SQL runned within aplication dosn't raise an errror but value from uniqueidentifier column is truncated. Help. (PB 7.0, MS SQL 7.0, OLE DB - SQLOLEDB) ...

Web resources about - PB 7.0 Client Cursor and MS SQL Server 7.0 - sybase.powerbuilder.database

MUD client - Wikipedia, the free encyclopedia
A MUD client is a computer application used to connect to a MUD , a type of multiplayer online game . Generally, a MUD client is a very basic ...

3Q Digital Offers Peek At 3Q Facebook Ad Performance By Its Largest Clients
With Facebook set to report its third-quarter earnings Wednesday , digital marketing agency 3Q Digital offered some insight on how the social ...

Gallop Labs hires former Facebook Client Partner as Director of Sales
Gallop Labs , a social marketing and analytics firm, announced that it has hired former Facebook Client Partner Andrew Peebles as the company’s ...

Lawyer labels client 'stupid' after New Year text to ex lands him behind bars for a week
Man's five days in prison for New Year text was significant &quot;wake-up call&quot;, lawyer says.

Canberra psychology clinic accidentally reveals clients' personal details in email
A Canberra psychology clinic has apologised after it accidentally shared personal details of hundreds of patients in a group email.

Beyond Biglaw: Categorizing Clients
In order to make a good decision about how to handle clients, it is important to assess their actual or potential contribution to the firm’s ...

Anchorage Assembly candidate drops out rather than reveal tutoring clients
... Anchorage Budget Advisory Commission, has withdrawn a bid for the Assembly because she did not want to list the names and addresses of clients ...

Spotlight On NW Creative: Fell Swoop And Its Unique Client Mix
After living in Seattle for a few years, it’s become clear to me that many shops here struggle to capture significant business from clients headquartered ...

New online FX broker group rails against client money laws
A group of online broking firms have launched a desperate bid to sway the government on its proposed client fund segregation laws.

SanDisk Announces X400 Client SSD for OEMs
... Like the X300, the X400 uses TLC NAND flash and relies on SLC-mode write caching to provide competitive write speeds. SanDisk OEM Client SSD ...

Resources last updated: 1/19/2016 4:39:44 PM