OK, So upon looking at the C++ resource files for the ODBC drivers, I see this 
section of code in plugin.cpp:

--------
if(  nPeriodicity == 24 * 60 * 60 &&
   oVar.m_pdate->hour == 0 &&
   oVar.m_pdate->minute == 0 &&
   oVar.m_pdate->second == 0 )
{
   qt->DateTime.PackDate.Hour = 31;
   qt->DateTime.PackDate.Minute = 63;
  qt->DateTime.PackDate.Tick = 15;
} else ...
--------

from looking at other parts of the code, it's clear that setting these values 
informs AB that the data is an EOD record if the database is an EOD database... 
I get that.  Makes sense that there is indeed a facility for this...
And I tested what I'm trying to do with an EOD database instead of 1min data, 
and that worked.

However, I'm still trying to get the seamless EOD/Intraday thing going like I 
have with my esignal feed, so I just want to rem out the nPeriodicity line for 
the moment and recompile and test.  I'm also noting along those lines that the 
nPeriodicity check is not part of the other instance of similar code that sets 
these EOD values.  Minimally, for testing purposes, I want to bypass the 
nPeriodocity DB check...

Anyway, has anyone else recompiled the ODBC.DLL's yet... ever, for any reason?  
I imported the files into MS Visual Studio VC++ 9.0 (2008), and I can get the 
DLLs compiled without any changes... but for some reason they don't get 
recognized by AB (yes, I copied them to the plugins dir).  I'm also noticing 
that the DLL sizes went from the original 44K to my 139K.

Admittedly, I'm not exactly a huge expert in C++ coding, but I generally know 
enough to get by, and have compiled, modified, and used several plugins for AB 
in the past.  For some reason, this one won't load once recompiled.  I suspect 
it has something to do with the conversion from the old Visual Studio format to 
2008.  Some unknown parameter I need to fix in the project perhaps.

Any ideas anyone?

Oh, and my sincere apologies to *Yofa*, whose name I misspelled in prior posts.

-Dan


Reply via email to