lalli_krishna
New member
- Joined
- Dec 7, 2007
- Messages
- 1
- Programming Experience
- 1-3
Hi All,
I used to maintain an application which used to exist in VB. To launch the VB modules we had a Smalltalk application using which we used to launch VB components and we used VBOrb to communicate between Smalltalk and VB. They used to work seamlessly.
Now we have migrated the VB components to VB.NET. The functionality of the system is just perfect without problems. But we see that randomly we seem to get VA Smalltalk Errors which make the Smalltalk application to crash and even my VB.NET application then. The same error can't be reproduced at the same point when I try again but it occurs at some other instance. This has become a very big problem in integrating the 2 systems.
Could someone who has some idea of the problem, please help me with the solution to this. Thanks in advance.
I used to maintain an application which used to exist in VB. To launch the VB modules we had a Smalltalk application using which we used to launch VB components and we used VBOrb to communicate between Smalltalk and VB. They used to work seamlessly.
Now we have migrated the VB components to VB.NET. The functionality of the system is just perfect without problems. But we see that randomly we seem to get VA Smalltalk Errors which make the Smalltalk application to crash and even my VB.NET application then. The same error can't be reproduced at the same point when I try again but it occurs at some other instance. This has become a very big problem in integrating the 2 systems.
Could someone who has some idea of the problem, please help me with the solution to this. Thanks in advance.