we investigate the access of the SQL.ini.
After each new connect the teamdeveloper searches the SQL.INI.
(See the attachment with the entries of the processmonitor)
The TD searches the SQL.ini in the current Directory. (filename normal and uppercase)
The TD searches the SQL.ini in the current Drive\root.
The TD searches the SQL.ini in the current Drive\sqlbase. (we haven't activated the sqlbase!!!)
The TD searches the SQL.ini in the Installation directory.
On my machine the SQL.ini is placed in the Installation - Directory. Now the TD finds the SQL.ini and opens the file with an lock. (Why a lock?)
(In the IDE the TD searches the SQL.ini only in the defined Directory of the preferences, not in the other directories. That's ok)
Is this procedure necessary? I think the TD should cache the infomation from the SQL.ini. There is too much access to this file, particularly when the SQL.ini is placed in an Network directory. And I don't understand why the SQL.INI must be read before each new connection?
Kind regards, Georg
Who is online
Users browsing this forum: No registered users and 3 guests