× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You can still use ODBC with C#.

The older IBM i drivers like ADO.Net and DAO still work, but I would use ODBC these days.

There are probably C#, Python, Node or PHP ways of merging word docs templates if you google them.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------

message: 5
date: Wed, 30 Oct 2024 18:12:16 -0400
from: Jim Franz <franz9000@xxxxxxxxx>
subject: Replacing Old Windows app retrieving Power i data for Word
docs merge

I'm preparing to talk to a contract Win developer unfamiliar with Power i tasked with rewriting a VB app from 2005 pulling data from a Power i via program calls and ODBC retrieve data.
The pc is an old Win 7 (maybe Win 98) and is around only because it still works.
The docs aren't changing (maybe 30 docs) and they want to keep in MS Word (Office 365) The old app merges mult docs with substituted data into a single email or print or even fax.

Is ODBC still in use? There is no SQL server in network, the user applications all either Power i or MS Office. No budget for big package, My code answers the current calls from Win and populates a DB2 table the Win app reads for the Word Merge. Most likely this will be a C# developer.

Google shows me lots of options (odbc, .net, etc) but many posts are 10 yrs old.
Without having to rewrite everything, what is a decent replacement to use in MS Word Merge?

Jim Franz



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.