Discussion of article "Practical Application Of Databases For Markets Analysis"

 

New article Practical Application Of Databases For Markets Analysis is published:

Working with data has become the main task for modern software - both for standalone and network applications. To solve this problem a specialized software were created. These are Database Management Systems (DBMS), that can structure, systematize and organize data for their computer storage and processing. As for trading, the most of analysts don't use databases in their work. But there are tasks, where such a solution would have to be handy. This article provides an example of indicators, that can save and load data from databases both with client-server and file-server architectures.

 

Author: Alexander

 
Great article! Really just the solution I was looking for. Unfortunately I'm having the same issue as Denkir commented on in the Russian version of this article.

It does not compile giving error:
'Values' - cannot call protected member function.

Associated with these lines in CBsvEngine::SaveData(void)
row.Values().GetValue(0).SetValue(TickBuffer[i].time);
row.Values().GetValue(1).SetValue(TickBuffer[i].bid);
row.Values().GetValue(2).SetValue(VolumeBuffer[i]);
And also the same error associated with numerous calls to 'Values()' in CDbDataAdapter::Fill(CAdoTable *table)   in the file DbDataAdapter.mqh

I would really love to get this working. Much appreciated!
 
can it be run in strategy tester? when i use adoSuite in strategy tester, it always terminate the program.
 
zephyrrr:

can it be run in strategy tester? when i use adoSuite in strategy tester, it always terminate the program.
Unfortunately the build 586 has an error in calling of 32-bit DLLs functions. It will be fixed in next build.
 
Automated-Trading:
Unfortunately the build 586 has an error in calling of 32-bit DLLs functions. It will be fixed in next build.
Unfortunately this haven't been solved after the last update. Any solutions or recommendations? how long this could take? I was told to wait until the next build and it came without solving the problem.