|
What we are trying to do is the following. We have a purchased Notes workflow application, (EtQ). We have a BPCS manufacturing package. We have a custom RPG program that generates what we call a Process Information, or PI, Sheet. This combines elements of: Bill of Materials, Routing, and Production Notes. We want this report in our Notes document. We were hoping to generate it using the following technique. Person enters part#, clicks on a button, and document is updated. We do not want to install ODBC on each client. We were hoping to use the AS/400 native ODBC for Notes. We were also hoping to use a stored procedure versus a bunch of SQL calls to data. Since the program is currently on the 400, why reinvent the wheel? The problem with the AS/400 native ODBC for Notes is that the activity has to run on the server, or it will try to use the client's ODBC. One way we thought of trying to get around it is to create an agent that will run when the document is created or modified. Then we would open and reclose the document automatically and display the new information. We just think this is a little kludgy and having to wait on the close/open, and, oh by the way, how long will it take until the agent actually runs on the server? We are not going to use the browser interface at this time. Although that would be nice in the fact that the script would then always be executing on the server and thus using the server ODBC. We've looked at DECS and have LEI but nothing there seems overly promising. Rob Berendt rob@dekko.com +--- | This is the Domino/400 Mailing List! | To submit a new message, send your mail to DOMINO400@midrange.com. | To subscribe to this list send email to DOMINO400-SUB@midrange.com. | To unsubscribe from this list send email to DOMINO400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: meechamw@ptd.net +---
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.