Comments on: Universal ODBC/SQL Data/AFL plugin http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/ News, Announcements, and more... directly from AmiBroker.com Tue, 17 Jul 2007 12:59:09 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: erez samo http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/comment-page-1/#comment-317 erez samo Fri, 08 Dec 2006 02:42:04 +0000 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/#comment-317 Hi Tomasz , I find the problem ! I was useing an XLS file as a data base, some how it couldnt read this file only if its a CSV file it can be read & transfered into AB , allso the file can be transferd into AB only if its closed . is there no way to the plugin to read the CSV file wile it is open & updating from & external source, do I have to save & close this file so the plugin then can pull data into AB ????? Hi Tomasz , I find the problem ! I was useing an XLS file as a data base, some how it couldnt read this file only if its a CSV file it can be read & transfered into AB , allso
the file can be transferd into AB only if its closed . is there no way to the plugin to read the CSV file wile it is open & updating from & external source, do I have to save & close this file so the plugin then can pull data into AB ?????

]]> By: erez samo http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/comment-page-1/#comment-316 erez samo Thu, 07 Dec 2006 22:34:44 +0000 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/#comment-316 Hi Tomasz , I don't get anny success with figgering this -ODBC/SQL Data/AFL plugin-, I followed the instruction but I dont get the Table name combo box with the list of available tables , it stay empty, anny idea what am I missing ? doing wrong ? thanks for your help,,,, Hi Tomasz , I don’t get anny success with figgering this -ODBC/SQL Data/AFL plugin-, I followed the instruction but I dont get the Table name combo box with the list of available tables , it stay empty, anny idea what am I missing ? doing wrong ?
thanks for your help,,,,

]]> By: AmiBroker DevLog » New ODBC/SQL plugin version 1.0.3 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/comment-page-1/#comment-172 AmiBroker DevLog » New ODBC/SQL plugin version 1.0.3 Thu, 03 Aug 2006 14:56:44 +0000 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/#comment-172 [...] See also announcement of version 1.0.0: http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/ [...] [...] See also announcement of version 1.0.0: http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/ [...]

]]> By: Tomasz Janeczko http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/comment-page-1/#comment-158 Tomasz Janeczko Sat, 22 Jul 2006 08:35:33 +0000 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/#comment-158 In my opinion, there is no need for special "support" for that. You can put tick data into database, just import them: combine date and time fields into single datetime field and put price and volume in separate fields, then in plugin configuration screen define open, high, low, close fields to point to single PRICE field that you have in your database. In my opinion, there is no need for special “support” for that.
You can put tick data into database, just import them:
combine date and time fields into single datetime field and put price and volume in separate fields,
then in plugin configuration screen define open, high, low, close fields
to point to single PRICE field that you have in your database.

]]> By: Steve Hite http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/comment-page-1/#comment-157 Steve Hite Fri, 21 Jul 2006 22:18:41 +0000 http://www.amibroker.com/devlog/2006/07/21/odbcsql-dataafl-plugin/#comment-157 Tomasz, Could you make the SQL/ODBC plugin a little more flexible so I could directly use a tick database? I have a lot of eSignal tick data and I'm currently using the following ASCII import format: $FORMAT Skip, Date_YMD, Time, Close, Volume $SKIPLINES 2 $SEPARATOR , $CONT 1 $GROUP 255 $AUTOADD 1 $DEBUG 1 $TICKMODE 1 Obviously, the first format line is the only important one for a database of ticks. The "Skip" is in there for the "T" or "Q" field. The date (YYMMDD) and time (HHMMSS) are separate fields. Here's a sample of what the data looks like (this is from an ER2 eSignal tick file): T,051229,001724,683.1,1, T,051229,003227,683,1, T,051229,003247,683,1, T,051229,003318,683,1, T,051229,003439,682.9,1, T,051229,003920,682.9,1, T,051229,003926,682.9,1, T,051229,004151,683.2,1, Thanks for considering this request. Tomasz,

Could you make the SQL/ODBC plugin a little more flexible so I could directly use a tick database? I have a lot of eSignal tick data and I’m currently using the following ASCII import format:

$FORMAT Skip, Date_YMD, Time, Close, Volume
$SKIPLINES 2
$SEPARATOR ,
$CONT 1
$GROUP 255
$AUTOADD 1
$DEBUG 1
$TICKMODE 1

Obviously, the first format line is the only important one for a database of ticks. The “Skip” is in there for the “T” or “Q” field. The date (YYMMDD) and time (HHMMSS) are separate fields. Here’s a sample of what the data looks like (this is from an ER2 eSignal tick file):

T,051229,001724,683.1,1,
T,051229,003227,683,1,
T,051229,003247,683,1,
T,051229,003318,683,1,
T,051229,003439,682.9,1,
T,051229,003920,682.9,1,
T,051229,003926,682.9,1,
T,051229,004151,683.2,1,

Thanks for considering this request.

]]>