|
I've never been a big fan of IBM's sample code, but it does show how it's done. However, that is COM and VB6 code, not VB.NET. Yes, via COM-Interop you could call the Client Access COM objects, but I would suggest a different way, especially from .NET. Create an RPG (or CL, or Cobol, or whatever) program that retrieved a DataQ entry and returned the value as a parameter. Then simply describe that program to SQL as a stored proc. Then tell your VB.Net programmers to call the stored proc via the .NET data provider just like any other stored proc and just like they are reading/updating data. There's no reason to special case the dataq access. In fact, the VB.Net programmers don't even have to know a DataQ is involved. -Walden ------------ Walden H Leverich III Tech Software (516) 627-3800 x11 WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
