Page 1 of 1

Some problems with UniDAC 3.00.0.10

Posted: Tue 06 Jul 2010 17:31
by invent
Hi,

yesterday I installed UniDAC 3.00.0.10 (full) instead of 2.70.0.9 for Delphi 7. After that I have some little problems:

1. More memory usage. In the Task Manager the memory for Delphi 7 raises up to 600 MB.

2. Unable to close Delphi. After compilation of a big project, I am unable to close Delphi. Only with "Kill Process" in the Task Manager.

3. The compiled Exe-File tries to open an TCP/IP-Connection to localhost (Message from my Firewall). Why???

4. Many Access-Violations in Oracle-Direct-Mode. Please look at special thread.

After that i deinstalled UniDac and i tried a new Installation with selected components: Only Oracle, Interbase and SQL-Server - Provider, no BDE-Migration and no CRDBGrid. Now Delphi works a little bit better.

1. The memory in Task-Manager still goes up to 600 MB.

2. Closing Delphi without problems.

3. Sorry, no information about TCP/IP, because I changed the firewall setting.

4. Oracle direct mode still crashes.

This is only for your information. I can live with the memory usage.

Kind regards,
Gerd Brinkmann
invent GmbH

Posted: Wed 07 Jul 2010 14:15
by bork
Hello

1. Does the Delphi 7 memory usage raise up to 600 MB for empty project or when you open a large project? For large projects memory usage depends on the project size.

2. We have never heard about such problem. If you help us to reproduce this problem then we will try to fix it.

3. We will check if compiled EXE tries to connect to localhost.

4. Oracle direct mode had problem with assigning connect if new connection is located in the DLL. I'll post an answer here: http://www.devart.com/forums/viewtopic.php?t=18211

Posted: Wed 07 Jul 2010 15:26
by invent
Hi again,

1. Sure, it's a large project and some DLLs in a project group. I think UniDac 3 takes more memory than UniDac 2.7. But it doesn't matters.

2. I'll try to reproduce this in the next days.

3. This is easy to check: Make in Delphi 7 a new empty project. Then place a TUniSQLMonitor on the form and start it. -> Connection to LoaclHost.

Kind regards,
Gerd Brinkmann
invent GmbH

Posted: Thu 08 Jul 2010 10:13
by bork
Hi

TUniSQLMonitor allows to send monitored data to any other application at the same computer or by the network. The network address, port, etc. is defined in the DBMonitorOptions property (empty Host value is equal to localhost). If you want to turn off sending monitored data by the network then you should set the Options.moDBMonitor option to False.

Also it seems like Delphi 7 hangs on closing if opened application has TUniSQLMonitor. We will notify you as soon as this this problem is fixed.

Posted: Fri 23 Jul 2010 14:51
by invent
Hi,

first I thought this is a joke, because setting Options.moDBMonitor option to False means, that I cannot use DBMonitor for debugging.

But after some tries I changed my code and now the user can set this option manually, so I can switch DBMonitor on or off. It was a litte bit tricky to give this information to any used DLLs.

Now everythings is fine. The "normal" user have no idea that there is a DBMonitor and so he has no problems with firewall. And the admins can switch DBMonitor on if required.

Thanks for this information. It was very helpful.

Kind regards,
Gerd Brinkmann
invent GmbH