Re: [foxboro] AIM*Historian connection on Windows
- From: Ales Vaupotic <ales.vaupotic@xxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 05 Nov 2004 16:39:44 +0100
As I can see, all the happy ODBC users are on 3.1.2 version of AIM*. We
must have 3.2. or later installed because of problems with Windows XP
pro SP1. At least we were told so. Are you guys using 3.1.2. on XP pro SP1?
Another observation: I have tested OLEDB 3.2.1 with different
environments and it seems to only work while in Visual Basic. As soon as
I use the COM object with ASP or PHP, it starts to misbehave. Any
suggestion? I think it has something to do with parameter passing by
value or by reference which works differently in ASP than in VB?!
Ales.
Michael Kessler wrote:
>I have been using this for over two years get legacy historian data. I'm
>grabbing about 2800 points (24 hours worth of data) out of the historian per
>day, every day. Now using Aim vs 3.1.2. Very few problems. I do find the
>ODBC interface slow, it takes almost two hours to grab all my data.
>
>
>
>>
>>There is a good example of usage of the AIM* ODBC driver with Visual Basic
>>and the DAO library (that works) in AIM*DataLink User's Guide (B0193YJ rev
>>B), section 10. As mentioned previously, the "Events" database should be
>>used to get alarms.
>>
>>
>>
>
>
>
>
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
