Re: [U2] UV to Access via ODBC - driver issue

2004-11-08 Thread John Koch-Northrup
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

 [EMAIL PROTECTED] 11/7/2004 8:44:55 PM 
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 driver, you may want to look at Fusionware. I don't recall if they

have something MS Access specific, but I suspect they do.

- Charles Dicing Up the Data Barouch

John Koch-Northrup wrote:

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 the server -
in Data Sources (ODBC) System DSN tab I have a pointer to a Microsoft
Access 2000 file.Screen sends an id to the Access database - a
total
number of parts on a reel is returned from the Access database and
placed into the screen.   It's been working nicely for about 6
months.

How it was broken:   

The system that stores data in the Access file was upgraded on
Thursday.   The Access file is now (I believe) at XP level.   The
ODBC
connection is broken.

Attempted fix (that failed):

Research on Microsoft's site led me to believe that upgrading to Jet
4.0 sp 8 and MDAC 2.8 would fix the problem.   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.   Admittedly - I thought that
was
an odd statement and I'm trying to get back to that article and read
it
through again. 

At the moment - I have the server sitting with Jet 4.0 sp 8 and MDAC
2.8 - and cannot connect to the Access file correctly.   Anyone run
into
something similar?  

Thanks!

John Koch-Northrup
---
u2-users mailing list
[EMAIL PROTECTED] 
To unsubscribe please visit http://listserver.u2ug.org/ 

  



-- 
 - Charles Barouch
 (718) 762-3884 x 1   - Key Ally Voice Mail

 [EMAIL PROTECTED]  - Consulting services
 [EMAIL PROTECTED] - News
 [EMAIL PROTECTED] - U2-Users Moderator

 [EMAIL PROTECTED]- Zeus Data Integration
 Mount Olympus, Home of Zeus Data Integration
---
u2-users mailing list
[EMAIL PROTECTED] 
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] UV to Access via ODBC - driver issue

2004-11-07 Thread Results
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 driver, you may want to look at Fusionware. I don't recall if they 
have something MS Access specific, but I suspect they do.

- Charles Dicing Up the Data Barouch
John Koch-Northrup wrote:
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 the server -
in Data Sources (ODBC) System DSN tab I have a pointer to a Microsoft
Access 2000 file.Screen sends an id to the Access database - a total
number of parts on a reel is returned from the Access database and
placed into the screen.   It's been working nicely for about 6 months.
How it was broken:   

The system that stores data in the Access file was upgraded on
Thursday.   The Access file is now (I believe) at XP level.   The ODBC
connection is broken.

Attempted fix (that failed):
Research on Microsoft's site led me to believe that upgrading to Jet
4.0 sp 8 and MDAC 2.8 would fix the problem.   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.   Admittedly - I thought that was
an odd statement and I'm trying to get back to that article and read it
through again. 

At the moment - I have the server sitting with Jet 4.0 sp 8 and MDAC
2.8 - and cannot connect to the Access file correctly.   Anyone run into
something similar?  

Thanks!
John Koch-Northrup
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/
 


--
- Charles Barouch
(718) 762-3884 x 1   - Key Ally Voice Mail
[EMAIL PROTECTED]  - Consulting services
[EMAIL PROTECTED] - News
[EMAIL PROTECTED] - U2-Users Moderator
[EMAIL PROTECTED]- Zeus Data Integration
Mount Olympus, Home of Zeus Data Integration
---
u2-users mailing list
[EMAIL PROTECTED]
To unsubscribe please visit http://listserver.u2ug.org/