We solved this issue... turns out I was chasing the wrong solution.
In reality, the data type of the ID in the Access database had been
changed from number to text.Where I was originally passing a SQL
statement of SELECT COLUMN FROM TABLE WHERE ID = 2 ... I switched it to
SELECT COLUMN FROM
drain"
- Montgomery Scott NCC-1701
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Koch-Northrup
Sent: Sunday, November 07, 2004 12:44 PM
To: [EMAIL PROTECTED]
Subject: [U2] UV to Access via ODBC - driver issue
I've been struggling through this one th
John,
>I found an article (which I oddly can't find now...) that stated that
Access beyond version 2000 no longer had a specific ODBC driver to connect
to it - you now connected through the Oracle driver.
I've just created a successful ODBC connection from Excel 2003 to Access
2003, so I don't t
Thanks for your response.This would be a great idea if the Access
database wasn't a realtime system.It's counting parts used on reels
from our machines on the shop floor and is constantly updated from
multiple sources.
Unless I'm not fully understanding what you're suggesting...
John
John,
You might want to patch it by exporting the Access data to a flat file
and push that into a UniVerse Type 19 where you can parse it. There are
third party tools [AD] including mine www.MtOlympus.us [/AD] that can
help you with the data conversion and parsing. If you need an alternate
ODBC
I've been struggling through this one the last few days - any help
would be GREATLY appreciated.
Platform: Dataflo 5.8.4 on Universe 10.0.10 on Win2000 sp 3 (though
I don't think Dataflo is an issue here...)
Previously working state:
Dataflo screen via the Universe BCI module calls ODBC on
