Hi. A few days ago install EWB 2.06b5 and also EDB 2.26b2 on a new computer. Until now I was developing with EWB 2.04b1 and EDB 2.24b1, without problems.
I have developments on Delphi XE3 that also worked well.
When installing EDB 2.26b2 and recompiling the applications, at the time of being loaded in the IDE of Delphi XE3, they showed the following error:
Property "LocalTempTablesPath" does not exist.
Also started to show the error applications made with EWB 2.06b5, which have an associated webmodule, developed in Delphi XE. (with EDBSession component).
Those applications that do NOT have webmodule, work well.
Check out the EDB forum and found an Incident Report # 4497 ​​dated 15-04-17, of the EDB version 2.25b1 with a similar problem.
Probe with EDBServer of 32 and 64 bits, giving the same error. (EDB 2.26b2 to EDB 2.25b1).
It does not "have" the property: "LocalTempTablesPath". EDB 2.24b1 has it.
The development platform I am using is Win7 Pro 64bits and Win2008 R2 (64bits). Delphi XE and Delphi XE3, with the latest versions of EWB and EDB now.
Regards
I am waiting for an answer to know if I am missing a step. Or if it is a new incident. Thanks...
Alvaro

Delphi applications do not have a problem since "refreshing" the form load and recording without the property: "Localtemptablespath", they work.
The real problem is webmodules that make use of the EDBSession component.

AlvaroRB


LocalTempTablesPath was moved from published to public in the last release or so. All you need to do if you have the component dropped on a form is to alter the pas file - add a space and delete it then save the file. Things should be ok after that.


Roy Lambert

Alvaro,

<< Probe with EDBServer of 32 and 64 bits, giving the same error. (EDB 2.26b2 to EDB 2.25b1).
It does not "have" the property: "LocalTempTablesPath". EDB 2.24b1 has it. >>

This is mentioned in the 2.25 breaking changes:

https://www.elevatesoft.com/download?action=info&category=edb&type=edbvcltrial&majorversion=2&version=2.26

You should always read the release notes, especially the breaking changes, in order to stay up-to-date with the changes/enhancements.  The release notes are always cumulative, so you'll see every breaking change/enhancement in reverse order from latest to earliest.

Tim Young
Elevate Software
www.elevatesoft.com

Roy, thanks for answering my problem. In Incident Report # 4497, Tim makes the same clarification as you indicate.

The error was mine ....

Change the ewmodule project to another folder, but do not delete the .dsk file.
Therefore the modifications of the .pas source were not those that were compiled. The .pas at the time of compiling was always the same.
Thanks again. Greetings to the group that always supports our doubts!

Thanks Tim for clarifying since there were changes. It is true that we need to be aware of the documented changes. My mistake I thought was simpler and "silly", for trying to work outside of working hours ....
Cordially
Alvaro