marcello62
Technical User
Hi there,
I'm maintaining a DLL written in Delphi 7. This DLL is compiled together with others to work together with an executable delivered by an external supplier. This executable is compiled from Delphi Sources but we don't have access to the sources. Every now and than this main program is updated, and we recompile our DLL's. Usually some small compile errors have to be fixed and it works. However, we don't get it working this time. We can correct and successfully recompile our sources, but when we close the app we get a runtime error:
'The instruction at ... referenced memory at ... The memory could not be read. click on Ok to terminate the program.'
This message re-appears 3 times (with different hexadecimal references), and than the following message appears:
'Runtime error 216 at ...'.
The strange thing is that the app does wat it has got to do!
But we can't leave our clients with these messages every time they shut down their apps.
The difficult thing here is that the first three errors are application errors thrown by the executable which we can't access the sources of.
Does anyone know what might be going on here? Any help will be greatly appreciated. Thanks.
I'm maintaining a DLL written in Delphi 7. This DLL is compiled together with others to work together with an executable delivered by an external supplier. This executable is compiled from Delphi Sources but we don't have access to the sources. Every now and than this main program is updated, and we recompile our DLL's. Usually some small compile errors have to be fixed and it works. However, we don't get it working this time. We can correct and successfully recompile our sources, but when we close the app we get a runtime error:
'The instruction at ... referenced memory at ... The memory could not be read. click on Ok to terminate the program.'
This message re-appears 3 times (with different hexadecimal references), and than the following message appears:
'Runtime error 216 at ...'.
The strange thing is that the app does wat it has got to do!
But we can't leave our clients with these messages every time they shut down their apps.
The difficult thing here is that the first three errors are application errors thrown by the executable which we can't access the sources of.
Does anyone know what might be going on here? Any help will be greatly appreciated. Thanks.