Jump to content


Photo
- - - - -

New Release Of ProIV


3 replies to this topic

#1 Rob Donovan

Rob Donovan

    rob@proivrc.com

  • Admin
  • 1,640 posts
  • Gender:Male
  • Location:Spain

Posted 11 March 2004 - 06:25 AM

A New kernel & client release is out.

Kernel 5.5 r333
Client 518

#2 Steve Kiernan

Steve Kiernan

    Advanced

  • Members
  • PipPipPip
  • 87 posts
  • Gender:Male
  • Location:United Kingdom
  • Interests:writing wonderful, professional, windows compliant systems in PROIV. Or not.

Posted 11 March 2004 - 04:06 PM

BEWARE!!!!

Those of you still using NATIVE to develop reports should be aware that they may not gen in this new release - the following is on PROIV.COM under the FAQ:

Q Why do I get the message 'SYSTEM E630' after upgrading to PROIV 5.5r333?

A This error message is produced for report functions when using a set of bootstraps from an earlier release with the 5.5r333 kernel. Several new error messages were introduced with 5.5r333, along with enhanced validation for XML report tags. Consequently the set of bootstraps provided with that release should be used.

The error message E630 ('630 - XML TAG NAME CONTAINS INVALID CHARACTER') is produced because no tag name has been assigned to a scratch variable field. Since it is possible to redirect a report at run time to produce XML output all report functions have their XML tags validated at gen time. If an XML tag is not specified the kernel will use the field tag name. If there is no field tag the XML tag will be set to the field name. Since scratch variables begin with either am octothorpe (#) or a dollar ($) symbol, which are invalid characters for an XML tag, this error message will be output.

To correct the problem you should upgrade to the latest bootstraps. This is done by exporting your functions from the earlier set and then importing them into the new set of bootstraps. You must not upgrade by extracting dbase.out or rbase.out into the existing bootstraps.

It is possible that this error message will also occur after upgrading correctly to the new set of bootstraps. This will happen if the native development environment is used to create or maintain report functions. To correct the problem in this situation the function exhibiting the error should be loaded into DeveloperStudio or VIP.




Another option is to put a tag yourself onto the report field by simply changing the contents of FLDSPEC.

Good one PRO-IV!

#3 Ross Bevin

Ross Bevin

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 226 posts
  • Gender:Male
  • Location:Manzanillo, Colima, Mexico

Posted 19 May 2004 - 12:33 PM

I have logged this bug with Pro-IV who have said they will fix it in the next release. In the mean time you can also export and reimport the function to fix the problem.

#4 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 19 May 2004 - 04:09 PM

Ross,

We have received a 334 pre-release (for testing) and I can confirm that the report issue is resolved.

Joseph



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users