Access to the data will either be via ERP clients local to each user
(Win2000/XP machines), or from home-grown windows apps (which, at the
moment, access MS SQL Server 7/2000 via ODBC, or OLEDB, or ADO).
The question is, do we actually _NEED_ HIS in this scenario; and if so,
does it _NEED_ to be integrated into MS SQL Server 7/2000 ? Or would a
good ODBC / OLE DB / ADO driver (on each client m/c?) be sufficient?
HYCH,
Rob
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
https://mvp.support.microsoft.com/communities/mvp.aspx
The short answer to why the data will in future be centralised on a
remote DB2 server, rather than locally on SQL Server is that our
corporate masters would have it that way. So we need to adapt and make
changes to our programs. The DB2 OLE-DB/ODBC driver seems the way to
go, much simpler than setting up HIS, and would involve the least
amount of disruption to the programs as possible. It would also give me
more time to port them to VS 2005/C# !
Rob
fyi - if you're running SQL Server then you should look into the "cut-down"
DB/2 ole-db driver that's downloadable as an add-on to MS SQL 2005. It's from
the HIS team, and is cut-down only in so much as the LU6.2 (HIS/SNA) stuff
isn't there - it only uses tcp-ip, which is all you need anyway.
Neil Pike. Protech Computing Ltd
Rob
Neil Pike. Protech Computing Ltd