× 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.



Forwarded for Dale:

----- Original Message -----
From: <DaleGindlesperger@fft-inc.com>
To: <mapics-l-admin@midrange.com>
Sent: Friday, June 21, 2002 10:54 AM
Subject: User-defined fields in MAPICS


> This is a general question/comment for the thread members.
>
> We use "user-defined fields" in the product structure files and other
> files to help support non-MAPICS functionality, such as union information
> requirements (labor standard type, etc).  When orders are released, the
> user-defined fields don't go over from the master files to the order files
> (ie., User Code A in PSTDTL doesn't go to MODATA).  It seems odd to me
> that we are forced to write blaster programs to load the user fields to
> the "work" files from the "master" files and either have them as triggers
> or insert them into the CLs.
>
> Here's where it is a question as well as a comment.  Have I been missing
> something in MAPICS that you can tell the system to copy the user fields
> over in order release and such?  Or is this a "functioning as designed"?
> If so, does it seem odd to you good people on the thread that they don't
> go over?
>
> I was going to write this up as an enhancement request, but if I am the
> only person that wants user fields to copy from the "master" to the "work"
> files, or if it will mess up other people's enhancements, I probably won't
> bother.
>
> Any comments one way or the other are welcome....
>
> Dale @ Fleetwood
>



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.