APAR status
Closed as documentation error.
Error description
Catvba-macro which was created on old-CATIA does not work on more recent CATIA level. CATIA VBA Macro Incompatibility between Releases is due to CATIA Library Re-organization. VBA Script made under CATIA environment is stored with library information in registory which is created at CATIA installation, and the library modules specified at make time are refered at run time. If library modules are re-organized (delete/rename etc.) in new release, Macros created previous release will fail. CAA documentation need to be updated with this MS restriction. .
Local fix
Problem summary
Catvba-macro which was created on old-CATIA does not work on mo re recent CATIA level. Catvba-macro which was created on old-CATIA does not work on more recent CATIA level. CATIA VBA Macro Incompatibility between Releases is due to CATIA Library Re-organization. VBA Script made under CATIA environment is stored with library information in registory which is created at CATIA installation, and the library modules specified at make time are refered at run time. If library modules are re-organized (delete/rename etc.) in new release, Macros created previous release will fail. CAA documentation need to be updated with this MS restriction. .
Problem conclusion
THIS MODIFICATION WILL BE INCLUDED IN CATIA DOCUMENTATION DELIVERED WITH CATIA VERSION 5 RELEASE 17. NOTE THAT DOCUMENTATION WILL ALSO BE INCLUDED IN V5R16SP02. Updated File: .../online/CAAScdInfTechArticles/CAAInfHints.htm CAA V5 Encyclopedia Automation Home What's New? Select the link Consult "About VB, VBA, Debug, and Portability" for details on manual adjustments that may be required for existing VB/VBA projects to be usable on a new release. Inter releases compatibility Obsolete Typelibs Some type libraries may become obsolete and disappear on a new V5 release. If an existing VBA project has references on a type library that doesn't exist anymore. If your access rights allow you to modify the Windows Registry, references to those libraries are automatically removed when opening the CATVBA file. If it's not the case, the following message may be experienced when launching a macro: CNEXT CATScriptError Message Scripting ERR_1000 Execute the script "XXXXX" |XXXXX= The script entry point could not be found. XXXXX Define a "CATMain" procedure which will be the entry point of the script. To avoid this, launch VBA (Alt-F11) and use the Tools/References menu item to launch the References panel. In this panel, uncheck the reference to the concerned type library and click on OK. This problem may also occur in VBA project of non V5 applications or in VB 6 projects. .
Temporary fix
Comments
APAR Information
APAR number
HD45749
Reported component name
CATIA V5 NT>XP
Reported component ID
569151000
Reported release
513
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-10-20
Closed date
2005-11-04
Last modified date
2005-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"513","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 November 2005