03-03-2020, 02:38 PM
Hi Guys,
A solution has been found. And the solution lies in line with a similar problem I had with an IW application and thread safe / session safe variables.
For the Web service it turns out to be the same rules that govern safety. All vars outside the web service Class definition, and its corresponding end, is not safe.
Having a datamodule with the ADO components on, I define the DM for the Web Service IMPL file, as dm : TApp2TBD; and in each procedure where I call a WS function or procedure, I create the DM with dm := TApp3TDB.Create(nil); just before the lines setting the ADO components up. And it's all wrapped in a try-final-end so the DM if Free'd up after use.
The problem was that the dm def "dm : TApp2TBD;" was outside the WebService Class / End definitions. IOnce I moved it to the private section, the problems dissapered.
Regards
Soren
A solution has been found. And the solution lies in line with a similar problem I had with an IW application and thread safe / session safe variables.
For the Web service it turns out to be the same rules that govern safety. All vars outside the web service Class definition, and its corresponding end, is not safe.
Having a datamodule with the ADO components on, I define the DM for the Web Service IMPL file, as dm : TApp2TBD; and in each procedure where I call a WS function or procedure, I create the DM with dm := TApp3TDB.Create(nil); just before the lines setting the ADO components up. And it's all wrapped in a try-final-end so the DM if Free'd up after use.
The problem was that the dm def "dm : TApp2TBD;" was outside the WebService Class / End definitions. IOnce I moved it to the private section, the problems dissapered.
Regards
Soren