Legacy data is such #&^@&
Maintaining an old vb3/Access 2.0 application. Don't laugh!!!! Believe it or not, it's highly critical to the org and not easily replaced. Runs to >40000 lines of code.
Anyway, I need to link data from a remote 32 bit Ingress DB via ODBC
I can link it the reverse way around using an Access 2k linked database and have the Access 2.0 DB receive the data, but I need to initiate things from the old 16 bit db which accepts the names of two querydefs and runs them.
It's all very confusing, I know, but simply, I need to implement connectivity between disparate sources.
Any REAL gurus - not wannabes - who find delight in software of historical significance, your assistance would be most welcome!
Rgds,
Case
[775 byte] By [
Case] at [2007-11-11 7:17:17]
# 2 Re: Legacy data is such #&^@&
Thanks very much for the reply.
It is my understanding that these drivers are in fact installed. being pretty ignorant about the Ingress DBA side of things (lets face it, being pretty ignorant about Ingress Full Stop....haven't used it since UNI!<G>)
By "link Data" I mean using Access 2.0 db to show selected table within the Acces Environment from the Ingress11 DB -and then creating a couple of queries in Access 2.0 to act on those table to generate a result which is required by the vb3 app.
Case at 2007-11-11 23:48:50 >
# 4 Re: Legacy data is such #&^@&
In Access 2.0, the options are a bit different...File/Attach Table/......Same thing I guess...
However, I am not offered an option of loading an Ingress data source. It simple doesn't appear in the list, although I know there is an Ingress DSN somewhere...installed by guys from the other site.
Before you ask, they are not much help....there is politics between sites...
Case at 2007-11-11 23:50:51 >
# 5 Re: Legacy data is such #&^@&
It may well be that you cannot create linked tables to 32-bit data sources from Access 2.0. It's been about a decade since I last used that application and Windows 95 had just been released. If interoperability was supported it may have only been available through Microsoft released ODBC drivers.
Here are your remaining options:
1) Try opening the database directly through DAO. Once again my memory is a little fuzzy on Access 2.0 but I think this capability is available using the OpenDatabase method. BTW, I saw an old newsgroup post that indicated you could use a couple of different 32-bit Ingress drivers from VB 3.0 (which would indicate DAO).
2) Create a 32-bit ActiveX EXE (not DLL) which operates at the interface to the Ingress data source. You would probably need to use arrays to pass the data back and forth which would probably eliminate any data binding possibilities if that is what you are using.
3) Upgrade to 32-bit versions of Access and Visual Basic, which is a technical option but may not be a business option.
