dohier
asked on
Pure virtual function call
Hello,
I'm under WIN98, VC 6.0 SP3, VB 6.0 SP3, MDAC 2.1. I wrote a VC 6.0 DLL that spawn SQL request using ODBC/ADO on a SQL AnyWhere database. Now I'm writing a VB program which is calling this DLL. The program still works but when I want to quit the VB program I got the message :"Runtime error! - R6025 - Pure virtual function call".
does somebody already have this kind of problem ?
regards,
Denis
I'm under WIN98, VC 6.0 SP3, VB 6.0 SP3, MDAC 2.1. I wrote a VC 6.0 DLL that spawn SQL request using ODBC/ADO on a SQL AnyWhere database. Now I'm writing a VB program which is calling this DLL. The program still works but when I want to quit the VB program I got the message :"Runtime error! - R6025 - Pure virtual function call".
does somebody already have this kind of problem ?
regards,
Denis
If should be a dll called mfc42.dll that comes with an Office2000 installation. You may find this dll several times on your system.
Check Microsoft Help DLL pages to check which one to hold and which one to drop
Check Microsoft Help DLL pages to check which one to hold and which one to drop
I don't know about a solution, but you could work around using an error trap to ignore the error and close anyway :)
Generally that error would occur when you have not supplied a function that you should have in your implementation.
VB expects the interface to be available and tries to call it.
If you are using COM in your DLL then I would expect that you hadn't implemented one of the functions defined in the interface.
Or you are calling a function through a pointer that has already been set to NULL.
Just speculation since you didn't post any code from either VB or within the DLL at the point that you receive the error.
VB expects the interface to be available and tries to call it.
If you are using COM in your DLL then I would expect that you hadn't implemented one of the functions defined in the interface.
Or you are calling a function through a pointer that has already been set to NULL.
Just speculation since you didn't post any code from either VB or within the DLL at the point that you receive the error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://msdn.microsoft.com/library/devprods/vs6/visualc/vccore/r6025.htm
http://support.microsoft.com/support/kb/articles/Q125/7/49.asp