Mike,
I'd very much appreciate the syntax for setting the LTPUR.
Thanks!
Bryan



On , Michael Ellis <michael.ellis@xxxxxxxxxxxxxxx> wrote:
Bryan,





You learned a valuable lesson without paying much for it.





Be VERY cautious about updating MAPICS tables with SQL. It can be done,


but only if you are CERTAIN you are performing all the logic that MAPICS


would do when you type in a green-screen or browser window and press enter.








Safe way to do this with a program is with SystemLink (oops - just reread


you're on 5.5 - no Syslink). It performs all the logic that MAPICS does


(since it IS MAPICS). If you do something with SQL, you'll need to


replicate the logic.


In your case, comletely fixable, just update the records by using an UPDATE


and set LTPUR=LTVEN+LTSAF.


Let me know if you need help with the syntax - I have to look it up but I


have one like it.


Mike











> ----------------------------------------------------------------------


>


> message: 1


> date: Mon, 6 Feb 2012 08:02:23 -0600


> from: Bryan Burns bryanburns599@xxxxxxxxx>


> subject: [MAPICS-L] LTPUR not recalculated after changing ITEMBL with


> SQL


>


> In an XA5.5 test environment, I updated LTVEN and LTSAF using SQL; but


> LTPUR has not been re-calculated for those items I updated.


>


> I went into ITEMBL file maintenace on a record and I was able to get it


> re-calculated that way.


>


> Two questions:


>


> 1. This was my first accomplishment using SQL to do an update and I'd like


> to know if I did any damage, and what other file/fields can be damaged with


> even the most careful use of SQL?


>


> 2. How can I automagically get the LTPUR recalculated for about 130


> records?


>


>

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2022 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.