|
Paola, I suspect that Lloyd is using IWP and was asking about how to join the files in an IWP subset specifically because he does NOT have the programmers needed to write the RPG code - right, Lloyd? ERLCOM and ERLIFM have done very little for me as an IWP user. You already have to know the relationships in order to understand what these two utilities are telling you - or have the source code, which we don't! -- Joan Joan McCready, IS Manager phone: 636-479-4499 MetalTek International fax: 636-479-3399 The Carondelet Division www.metaltekint.com 8600 Commercial Blvd Pevely, MO 63070 -----Original Message----- From: pgroeber@bellsouth.net [mailto:pgroeber@bellsouth.net] Sent: Friday, September 27, 2002 6:34 AM To: mapics-l@midrange.com Subject: Re: IFM/COM QUESTION Lloyd, IFM was written by another company and later integrated with COM. Have you looked at the Entity Relation Tools called ERLCOMn or ERLIFMn (n=Release level, e.g. ERLCOM5 or ERLCOM6)? A programmer will have to know the files and fields in both applications as there are some fields in COM that do not map to IFM and vice versus. There isn't any quick reference other than these two tools to help understand the files if you do not have SYNON and the source code. Another idea would be to write programs to harvest the fields from the files you want and set up your own data warehouse set of files for using for your reports. It could be updated nightly so that data on reports would only be up to 24 hours old. That way you could cut down on the number of "joins" you needed and structure the files the way 'you' need them. It would take a programmer though that really know the content of the files or is proactive enough to research the data in the files. Just some ideas that hopefully can help you. The two tools ERLCOMn and ERLIFMn are available from MAPICS free. Hope this helps. Paola Groeber MAPICS Consultant 770-591-1497 > > From: "LLOYD DEGNON" <ldegnon@email.com> > Date: 2002/09/26 Thu PM 03:48:58 EDT > To: mapics-l@midrange.com > Subject: IFM/COM QUESTION > > [ Converted text/html to text/plain ] > Has anyone out there figured out a clever way to relate the IFM file > YAAFREP(entity master-bill to info) to the COM file CUSMAS(ship to > info)??? No common keyed fields, MAPICS insiders say that internal > code handles the linking relationship between the two in IFM. This is > a Real big problem for those of us who need to use things like IWP to > write reports! Kinda funny that using a report writer from MAPICS > can't get me what I need! It would be sooo simple for MAPICS to add a > keyed field in both files to allow joins! Oh well, go figure... > Anyhow, has anyone else out there solved this? > Thanks, > Lloyd H. Degnon > I. S. Manager > Ampro Computers Inc. > 5215 Hellyer Ave > San Jose, CA 95138 > 408.360.4365 > Ldegnon@ampro.com > http://www.ampro.com[1] -- > > _______________________________________________ > Sign-up for your own FREE Personalized E-mail at Mail.com[2] > > ===References:=== > 1. http://WWW.AMPRO.COM > 2. http://www.mail.com/?sr=signup > > _______________________________________________ > This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To > post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, > or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l > or email: MAPICS-L-request@midrange.com > Before posting, please take a moment to review the archives at > http://archive.midrange.com/mapics-l. > > _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mapics-l or email: MAPICS-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.
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.