For no specific reason the Visual Basic development environment crashes. Install Service Pack 5.
You may receive a "LINK: fatal error LNK1104…." on the final stages of a Visual LANSA component compile. This is caused by the Visual Basic development environment locking components if they are referenced e.g. if they are added to its component toolbar. Close Visual Basic and re-compile Visual LANSA component.
As Visual Basic form layouts are not available in the source you must either:
1. Use Notepad to cut/paste the supplied object source into a Visual Basic form prior to viewing them
2. Add the controls manually using the screen captures included in the provided examples as a basis.
Either your Session Initialization (see Setup Tasks) file (session.cfg) is not valid or can't be found. Check the parameters are correct and that the file session.cfg contains the correct information.
After Making an executable, running the application from the Visual Basic 6.0 environment behaves oddly. Calls to LANSA ActiveX components may fail. If there are multiple embedded Visual LANSA Panels, they may all look the same. This is caused by some incorrectly cached information in Visual Basic 6.0. This may improve on the second invocation, and will be fixed by quitting Visual Basic 6.0 and restarting.
Visual Basic 6.0 does not like an event with an underscore ( '_' ) in the name, this may make all events fail! In Visual LANSA, change the 'Name' property in the event's ActiveX attribute and recompile eg:
Attribute Class(#PRIM_ATTR.AX_EVT_MEMBER) Dispid(9) Name('OKButtonPressed')