Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Select error SQLSELECT=01S01

5 posts in PB Infomaker Report Writer Last posting was on 1999-05-20 13:28:14.0Z
Doreen Weekley Posted on 1999-04-27 17:13:50.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Select error SQLSELECT=01S01
Date: Tue, 27 Apr 1999 13:13:50 -0400
Lines: 19
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_XVgb5ANk#GA.302@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6400
Article PK: 241390

I have been using version 2.01 of the Pervasive 32bit ODBC driver for
reporting against Btrieve data without any problems for a number of months.
Recently I upgraded to version 2.04 and using the same data, same reports I
now get the following error:

Select error SQLSELECT = 01S01
[Pervasive Software][ODBC Interface] Error in Row(655)

The row is not always 655, I've also seen Row(1000).
I've tried a new report on one single table and it runs when I select about
8 columns. When
I select more I get the above message. I've compared registry settings from
what they are when 2.01 installs and they appear the same with 2.04. Do you
have any suggestions?

Thanks ahead of time for any suggestions you might have.
Doreen


Terry Dykstra Posted on 1999-04-27 18:37:40.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: Select error SQLSELECT=01S01
Date: Tue, 27 Apr 1999 12:37:40 -0600
Lines: 37
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_Yk7RAyNk#GA.302@forums.sybase.com>
References: <348_XVgb5ANk#GA.302@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6399
Article PK: 241385

I would start with deleting the PBCATxxx tables. They will be automatically
recreated when you login again. There probably is a difference in the
definition files between 2.01 and 2.04.
If that doesn't solve it, you got a serious problem in that the internal
ODBC calls have changed between the ODBC drivers. Turn on a trace at the
ODBC level. This will generate a very detailed log of what is happening.
You set this through the ODBC Administrator. Then run the report using the
2.01 and the 2.04 drivers. These logs you should submit to the Pervasive
people.

--
Terry Dykstra (TeamPS)
Canadian Forest Oil Ltd.

Doreen Weekley wrote in message ...
>I have been using version 2.01 of the Pervasive 32bit ODBC driver for
>reporting against Btrieve data without any problems for a number of months.
>Recently I upgraded to version 2.04 and using the same data, same reports I
>now get the following error:
>
>Select error SQLSELECT = 01S01
>[Pervasive Software][ODBC Interface] Error in Row(655)
>
>The row is not always 655, I've also seen Row(1000).
>I've tried a new report on one single table and it runs when I select about
>8 columns. When
>I select more I get the above message. I've compared registry settings
from
>what they are when 2.01 installs and they appear the same with 2.04. Do
you
>have any suggestions?
>
>Thanks ahead of time for any suggestions you might have.
>Doreen
>
>


Doreen Weekley Posted on 1999-05-14 10:44:14.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Re: Select error SQLSELECT=01S01
Date: Fri, 14 May 1999 06:44:14 -0400
Lines: 64
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_DF6fRWfn#GA.152@forums.sybase.com>
References: <348_XVgb5ANk#GA.302@forums.sybase.com> <348_Yk7RAyNk#GA.302@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6324
Article PK: 241309

An FYI in case anyone else encounters this problem, it can be resolved as
follows:
InfoMaker/Powerbuilder chooses the row set size that is greater than the
maximum data buffer that can be allocated by the driver. This causes errors
to be returned. To resolve this problem the Database Profile which uses the
Pervasive ODBC driver needs to be configured as follows:

1) Select File/Power Panel or Press Ctrl+Shift+N
2) Highlight "Database Profile"
3) Click on the Ok button.
4) Highlight the appropriate Profile in the ODBC Folder.
5) Click on the Edit button.
6) Click on the Transaction tab.
7) Click on the edit box beside the text "Retrieving Block Factor"
8) Enter 20

The retrieving block factor can be up to 100 but I began to get errors on
numbers higher
than 20.

Terry Dykstra wrote in message ...
>I would start with deleting the PBCATxxx tables. They will be
automatically
>recreated when you login again. There probably is a difference in the
>definition files between 2.01 and 2.04.
>If that doesn't solve it, you got a serious problem in that the internal
>ODBC calls have changed between the ODBC drivers. Turn on a trace at the
>ODBC level. This will generate a very detailed log of what is happening.
>You set this through the ODBC Administrator. Then run the report using the
>2.01 and the 2.04 drivers. These logs you should submit to the Pervasive
>people.
>
>--
>Terry Dykstra (TeamPS)
>Canadian Forest Oil Ltd.
>Doreen Weekley wrote in message ...
>>I have been using version 2.01 of the Pervasive 32bit ODBC driver for
>>reporting against Btrieve data without any problems for a number of
months.
>>Recently I upgraded to version 2.04 and using the same data, same reports
I
>>now get the following error:
>>
>>Select error SQLSELECT = 01S01
>>[Pervasive Software][ODBC Interface] Error in Row(655)
>>
>>The row is not always 655, I've also seen Row(1000).
>>I've tried a new report on one single table and it runs when I select
about
>>8 columns. When
>>I select more I get the above message. I've compared registry settings
>from
>>what they are when 2.01 installs and they appear the same with 2.04. Do
>you
>>have any suggestions?
>>
>>Thanks ahead of time for any suggestions you might have.
>>Doreen
>>
>>
>
>


Terry Dykstra Posted on 1999-05-14 14:41:49.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: Select error SQLSELECT=01S01
Date: Fri, 14 May 1999 08:41:49 -0600
Lines: 73
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_2P8Yjdhn#GA.313@forums.sybase.com>
References: <348_XVgb5ANk#GA.302@forums.sybase.com> <348_Yk7RAyNk#GA.302@forums.sybase.com> <348_DF6fRWfn#GA.152@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6321
Article PK: 241307

How did you find that solution?

--
Terry Dykstra (TeamPS)
Canadian Forest Oil Ltd.

Doreen Weekley wrote in message ...
>An FYI in case anyone else encounters this problem, it can be resolved as
>follows:
>InfoMaker/Powerbuilder chooses the row set size that is greater than the
>maximum data buffer that can be allocated by the driver. This causes errors
>to be returned. To resolve this problem the Database Profile which uses the
>Pervasive ODBC driver needs to be configured as follows:
>
> 1) Select File/Power Panel or Press Ctrl+Shift+N
> 2) Highlight "Database Profile"
> 3) Click on the Ok button.
> 4) Highlight the appropriate Profile in the ODBC Folder.
> 5) Click on the Edit button.
> 6) Click on the Transaction tab.
> 7) Click on the edit box beside the text "Retrieving Block Factor"
> 8) Enter 20
>
>The retrieving block factor can be up to 100 but I began to get errors on
>numbers higher
>than 20.
>
>Terry Dykstra wrote in message ...
>>I would start with deleting the PBCATxxx tables. They will be
>automatically
>>recreated when you login again. There probably is a difference in the
>>definition files between 2.01 and 2.04.
>>If that doesn't solve it, you got a serious problem in that the internal
>>ODBC calls have changed between the ODBC drivers. Turn on a trace at the
>>ODBC level. This will generate a very detailed log of what is happening.
>>You set this through the ODBC Administrator. Then run the report using
the
>>2.01 and the 2.04 drivers. These logs you should submit to the Pervasive
>>people.
>>
>>--
>>Terry Dykstra (TeamPS)
>>Canadian Forest Oil Ltd.
>>Doreen Weekley wrote in message ...
>>>I have been using version 2.01 of the Pervasive 32bit ODBC driver for
>>>reporting against Btrieve data without any problems for a number of
>months.
>>>Recently I upgraded to version 2.04 and using the same data, same reports
>I
>>>now get the following error:
>>>
>>>Select error SQLSELECT = 01S01
>>>[Pervasive Software][ODBC Interface] Error in Row(655)
>>>
>>>The row is not always 655, I've also seen Row(1000).
>>>I've tried a new report on one single table and it runs when I select
>about
>>>8 columns. When
>>>I select more I get the above message. I've compared registry settings
>>from
>>>what they are when 2.01 installs and they appear the same with 2.04. Do
>>you
>>>have any suggestions?
>>>
>>>Thanks ahead of time for any suggestions you might have.
>>>Doreen
>>>
>>>
>>
>>
>
>


Doreen Weekley Posted on 1999-05-20 13:28:14.0Z
Newsgroups: sybase.public.infomaker.general
From: "Doreen Weekley" <dweekley@primavera.com>
Subject: Re: Select error SQLSELECT=01S01
Date: Thu, 20 May 1999 09:28:14 -0400
Lines: 85
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_wDi40Nso#GA.225@forums.sybase.com>
References: <348_XVgb5ANk#GA.302@forums.sybase.com> <348_Yk7RAyNk#GA.302@forums.sybase.com> <348_DF6fRWfn#GA.152@forums.sybase.com> <348_2P8Yjdhn#GA.313@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6298
Article PK: 241283

Actually I just passed the problem on to our internal ODBC "expert". He did
some tracing
and suspected the problem was related to extended fetching. He searched the
Powerbuilder
Knowledge base using ExtendedFetch, I believe, and found a solution.

Terry Dykstra wrote in message <2P8Yjdhn#GA.313@forums.sybase.com>...
>How did you find that solution?
>
>--
>Terry Dykstra (TeamPS)
>Canadian Forest Oil Ltd.
>Doreen Weekley wrote in message ...
>>An FYI in case anyone else encounters this problem, it can be resolved as
>>follows:
>>InfoMaker/Powerbuilder chooses the row set size that is greater than the
>>maximum data buffer that can be allocated by the driver. This causes
errors
>>to be returned. To resolve this problem the Database Profile which uses
the
>>Pervasive ODBC driver needs to be configured as follows:
>>
>> 1) Select File/Power Panel or Press Ctrl+Shift+N
>> 2) Highlight "Database Profile"
>> 3) Click on the Ok button.
>> 4) Highlight the appropriate Profile in the ODBC Folder.
>> 5) Click on the Edit button.
>> 6) Click on the Transaction tab.
>> 7) Click on the edit box beside the text "Retrieving Block Factor"
>> 8) Enter 20
>>
>>The retrieving block factor can be up to 100 but I began to get errors on
>>numbers higher
>>than 20.
>>
>>Terry Dykstra wrote in message ...
>>>I would start with deleting the PBCATxxx tables. They will be
>>automatically
>>>recreated when you login again. There probably is a difference in the
>>>definition files between 2.01 and 2.04.
>>>If that doesn't solve it, you got a serious problem in that the internal
>>>ODBC calls have changed between the ODBC drivers. Turn on a trace at the
>>>ODBC level. This will generate a very detailed log of what is happening.
>>>You set this through the ODBC Administrator. Then run the report using
>the
>>>2.01 and the 2.04 drivers. These logs you should submit to the Pervasive
>>>people.
>>>
>>>--
>>>Terry Dykstra (TeamPS)
>>>Canadian Forest Oil Ltd.
>>>Doreen Weekley wrote in message ...
>>>>I have been using version 2.01 of the Pervasive 32bit ODBC driver for
>>>>reporting against Btrieve data without any problems for a number of
>>months.
>>>>Recently I upgraded to version 2.04 and using the same data, same
reports
>>I
>>>>now get the following error:
>>>>
>>>>Select error SQLSELECT = 01S01
>>>>[Pervasive Software][ODBC Interface] Error in Row(655)
>>>>
>>>>The row is not always 655, I've also seen Row(1000).
>>>>I've tried a new report on one single table and it runs when I select
>>about
>>>>8 columns. When
>>>>I select more I get the above message. I've compared registry settings
>>>from
>>>>what they are when 2.01 installs and they appear the same with 2.04. Do
>>>you
>>>>have any suggestions?
>>>>
>>>>Thanks ahead of time for any suggestions you might have.
>>>>Doreen
>>>>
>>>>
>>>
>>>
>>
>>
>
>