|
Paul, I have been trying to figure out which way would be best for a long time now. Luckily the scope on my project has changed so many times that I have not had to make a decision yet. I am hoping that the Virtual "stuff" in LEI 6 will be the answer. With that the data can stay in DB2 and it can be accessed as if it was in Notes with no real extra amount of coding. I personally don't like the idea of having data in two places and trying to keep them in snyc. So far I am leaning towards using LSXLC in Notes to get the data from the back-end when needed. At least that is what I will have to go with until I can get my hands on LEI 6. -- ------------------------------------------------------ Scott P. Johnson Applications Development Team Coordinator Microcomputer Development Specialist IBM Certified Specialist - AS/400 RPG Programmer Highsmith Inc. W5527 Hwy 106, PO BOX 800 Fort Atkinson, WI 53538-0800 TEL: 920-563-9571 FAX: 920-563-7395 sjohnson@highsmith.com www.highsmith.com ------------------------------------------------------ I've got a client who is in the process of developing a purchasing application in Domino. The discussion they are now having relates to performance. Their RPG programmer thinks that they will get acceptable performance by doing lookups of vendors, G/L account numbers, etc., by passing these parameters to the accounting system machine and getting responses back. The Domino programmer is saying that they need to have "duplicate" databases on the accounting system machine and the Domino machine, and then just keep them in synch. When these master files are updated on the accounting system machine, a program can be written to push this data into work files that can then be retrieved by the Domino machine using an agent that runs on a frequent basis. --
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.