5 replies to this topic

[Rob Donovan]

A New kernel & client release is out.

Kernel 5.5 r308
Client 505

[Ross Bevin]

During testing of this new version today I discovered the ALIAS command is not working as it should, in a Windows 2000/SQL Server 2000 environment. Pro-ISAM works fine. It seems as though that once a file definition has been altered by an ALIAS command, the file definition permanently points to that physical file for the duration of the Pro-IV session. All other ALIAS commands on that file are ignored. Worse still, all functions using the same file definition without ALIAS commands will also point to the last ALIAS physical file. Once you log off the ALAIS is cleared. I have logged this bug with Pro-IV and will keep you posted.

PS: The sort/select bug I reported for SQL in the previous release has now been fixed in this release.

Ross Bevin

[Ross Bevin]

Pro-IV has accepted this as a bug, but they do have a work around. I was told to place the following command in pro4.ini and it fixed the problem.

REPARSE=Y

This ALIAS bug was also a problem on our production server running 5.5 r216.

Ross Bevin

[Rob Donovan]

Hi,

Just a word of warning, using REPARSE=Y could produce performance problems, since every SQL statement is 'rephrased' every time.

Rob D.

[Rob Donovan]

Hi Ross,

We are testing ProIV 5.5r308 with our system, and have come accross this bug.

There does not seem to be a new version of ProIV to fix this...

Did you ever get any response from ProIV LTD to this bug, since setting the REPARSE flag is something we do not want to do.

Thanks,

Rob D.

[Rob Donovan]

FYI:

After talking to ProIV LTD, there has been no bug fix yet

Its seems to affect all versions / platforms with 5.5 and Oracle.

We looked into using the REPARSE=Y flag, but this makes all SQL take about twice as long

We are now a bit stuck....

Rob D.