Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
We put the ODBC driver through some abuse on a daily basis. It's one of the most under appreciated drivers in Geo SCADA as far as I'm concerned. Honestly -- it's great. If you don't use it for things, find a way to use it, your life will change for the better.
That said -- a common use case for us is for importing data from a CSV or a text file. The CSV/text file might get auto-populated at x period throughout the day. The issue we run into is that the file itself is "locked" when the ODBC driver is in service. Our work around is to schedule around the scan rate and disable the driver during the time that the file should be refreshed.
I think what makes sense here is that the file should really only be accessed during scans. We understand it's an ODBC source and treat it similar to an internal point where we would control the quality. There's no reason to keep the file locked when a scan is not active. Note that if your ODBC source is a database and you run a normal query, nothing gets locked. It's really only when using file based ODBC sources that I've seen the issue. Maybe it's a Windows thing, but surely there's a way to "disable" the scan and unlock the file inbetween scan rates.
The image below is what you see when you try to open a file that is used in a ODBC query, despite the scan rate for the query object being 1H (once an hour).
3 Comments
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.