|
>> It was simply an option for creating thick client interfaces that used a language most AS/400 programmers were already familiar with. The other aspect as it pertains to this discussion is that by default VARPG accesses the OS/400 DB when you do CHAIN, READ, whatever. It has limited support for handling local PC files other than through an ODBC interface. Having a thick client that was oriented around the AS/400 as _the_ server was a priority in the design and development of the product. Contrast that with ASNA (map to any DB via their engine); California Software (emulates a 400 on a PC), and VB (Windows based DB). Jon Paris Partner400 www.Partner400.com www.RPGWorld.com
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.