Re: [foxboro] AIM*Historian connection on Windows
- From: Ales Vaupotic <ales.vaupotic@xxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 04 Nov 2004 07:20:54 +0100
Jim,
Pan, Jim wrote:
>I never used AIM*API function calls, but I did use AIM*ODBC for other
>applications to query event messages from AIM*Historian.
>
>The first thing I would do is to check the "Logging Msgs" field of the
>message Names (such as ALARMMESG, OPRACTION, and SYSMONMSG). Setting the
>field to "Yes" will make these event messages available to ODBC access.
>
>The next I would do is to test the ODBC connection with MS Access. You need
>to define a new DSN to access the "Event Messages" database, not the
>"Message" database. Make a linked table from Access to AIM*Historian using
>this "Event Messages" ODBC connection and see if you can get any event
>messages from Access Query.
>
>
>
I have done that already and it only works in Access 97. Even there with
some minor hickups. With any other tool (Office XP or 2003, VB6, Delphi,
ASP, PHP, VC) which offers ODBC connection I can't connect to the
source on my machine. Usually the driver fails with "Catastrophic
Failure" message. With OLE*DB I got a bit closer but there was the other
problem I described.
>Jim Pan
>Lifetime Learning Center
>Houston
>
>
>
Can you post the version of software and operating system you work with?
Ales Vaupotic
AMI
Ptuj, Slovenia
_______________________________________________________________________
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:
