Page 1 of 1

DBMONITOR stopped working

Posted: Mon 29 Apr 2013 19:10
by wilton_radinfo
After upgrading to version 6.7.13 of the SDAC commands are not sent to the dbmonitor.

all applications were recompiled the dbmonitor no longer works.
I tried to add some units, but not worked well.

DASQLMonitor, MSSQLMonitor, DBMonitorMessages, DBMonitorClient,
StdCtrls, DB, MemDS, DBAccess, MSAccess, sdacvcl;


ps:
the option to debug this ok

Re: DBMONITOR stopped working

Posted: Mon 29 Apr 2013 19:15
by wilton_radinfo
I discovered that a new property has been created and is disabled by default

options / moDBmonitor = True

Re: DBMONITOR stopped working

Posted: Tue 30 Apr 2013 09:18
by AndreyZ
From now, the TMSSQLMonitor.Option.moDBMonitor property is set to False by default. It is done to avoid showing of the 'Socket error 10061' error when the application is run from IDE and there is no dbMonitor running.
To solve the problem, you should set the TMSSQLMonitor.Option.moDBMonitor property to True.
Please note that we did not add the moDBMonitor option, it was in previous versions of SDAC. We just changed its default value from True to False.