Are there any instances where you cannot free a 'created' object? The only reason I ask is I have created an object and when I try to free it I get an access violation. Obviously I'm concerned that the object is created but never freed, using up resources.
I have never seen this behaviour before when using create/free.
But the scenario for this is slightly different to normal, for me anyway. I am using a class created by the WSDL importer.
Does this react any differently to a normal class create and free scheme?
The example I am working on is quite big, so I don't really want to post it all here. I hope I've given enough outline for someone bo be able to help? if you need more information, I can supply it.
Created in the WSDL import unit:
TransactionRequest = class;
TransactionRequest = class(TRemotable)
In my code, I have (simplistcally):
objTransactionRequest : TransactionRequest;
It's the 'free' line that fails wth an access violation. This is something to do with being a TRemotable decendent?
What can I do to ensure the object is released correctly?