Problem with ADO Dataset Iterator

FinalBuilder Bugs
1

 

I have a finalBuilder script which has a problem with the ADO Dataset Iterator

I am using a Query, which in SQL Plus returns 146 rows, but in the FinalBuilder script the same query only returns 100 rows. I need all 146 rows.

I am trying to get the records from an Oracle 9.2 database via an ODBC Oracle connection.

The connectionstring looks like this:

Provider=OraOLEDB.Oracle.1;Password=xxxxxx;Persist Security Info=True;User ID=harvest;Data Source=HARVEST.INTRA.COOP

Do I miss an option somewhere ?

Can you help.

2

Hi John,

Thanks for reporting this. There was a bug in the way we were reading the available record count from the ADO provider, some providers worked and some did not.

We now have a fix for this problem. There is a test build that should work for all providers, it can be downloaded from this URL:

https://www.finalbuilder.com/downloads/finalbuilder/550/FB550_439.exe

Please let us know how you go.

Regards,

Angus

3

Hi Angus

Thank you very much for the fix. It solved the problem with the limitation af 100 rows, now we get all the rows.

But however the fix introduced a new problem.

When the query returns with a number of rows and we have a loop doing some work on every row, the last row is not affected.

ex. If there are 50 rows in the query-result only the 49 first rows are running through the lopp, not the last row.

We can take care of the last rows seperately, but in cases where the query returns 0 rows we have a problem.

Can you help.

John

4

Hi John,

I can confirm this. Sorry, I must have missed it when I was testing it out yesterday.

Here's another test build with a fix for the introduced bug. Sorry for the inconvenience of two downloads.

https://www.finalbuilder.com/downloads/finalbuilder/550/FB550_442.exe

Regards,

Angus

5

Hi Angus

Thank you for the new fix. Our problem with the ADO Dataset Iterator has been fixed.

However I am sorry to inform you that the fix has introduced another bug, a little more serious.

We have noticed a change in the Build VS.Net Solution Action Block

The output path for MSBuild is missing, We no longer get the folder: …\bin\Release_PublishedWebsites…

When running a build on a solution file created in Visual Studio 2005 to Release using MSBuild the difference from the 2 versions commands are:

Old command in version 5.5.0.60
Running C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe with parameters : “C:\Coop\Applikation\WebConfigSystem\WebConfigSystem.sln” /t:Build /p:Configuration=“Release”;Platform=“Any CPU”;OutputPath=“bin\Release”

Command in version 5.5.0.442
Running C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe with parameters : “C:\Coop\Applikation\WebConfigSystem\WebConfigSystem.sln” /t:Build /p:Configuration=“Release”;Platform=“Any CPU”

We need the output path. Can you correct this ?

Regards

John

6

Hi John

I can answer this one, since I was the one who checked in that change. During the VS2005 beta, it became apparent that when the platform was set to Any CPU, the ouput path for the project was being ignored and we could not predict where the output would go. So we added some code to hard code the output path. A while back we realised that this had been fixed in the release version of VS2005 so we removed the work around. If you specify an output path in VS it should be used.