[Tino Lopez]

Yes, Pietro if you can please share that script, it would be much appreciated.

[Tino Lopez]

Yes, we have been working with UAC disabed.

[Tino Lopez]

Thanks Mike, I did not know that, that can most definitely happen. Has CC identified this as an issue?

Pietro, This is the error: An error (-2147417851) occurred, however the MAPI subsystem did not specify detailed information about this error

[Tino Lopez]

Thank you for responding. It is 32 bit. Yes, you are correct, Quantum does not play well with 64 bit.

[Tino Lopez]

Thank you very much Pietro. It is very much appreciated.

tino.lopez@barfieldinc.com

[Tino Lopez]

Thank you David.

[Tino Lopez]

Thank you. That worked.

[Tino Lopez]

Thank you for all your help. I found that the USER_FIELDS table contains a list of users with their corresponding fields. If a user exists in this table assigned to a field(listed in the FIELDS_LIST table), the user wil be unable to access the field. You need to remove the user form the USER_FIELDS table in order to give them right to do so. We have many users and we needed to find a way to quickly restore access to these fields.

[Tino Lopez]

Sorry for not being more specific. I need to create a script that assigns the rights to release the WO. I know of the permissions which controls access to the user but the way this box works in our system is by field name restriction or “Field Restrictions” within Maintain User Security Profiles”. Please see the screenshot I attached.

[Tino Lopez]

Thank you for the response but I am looking for where within the database I can find the field that control access to this Release.

[Tino Lopez]

Thank you

[Tino Lopez]

Thank you

[Tino Lopez]

Thank you

[Tino Lopez]

That worked, thank you.

[Tino Lopez]

Thank you very much. I will try that and let you know the results.

[Tino Lopez]

Sorry for the late response. No, XML templates being used in the event.

[Tino Lopez]

Thank you for all the replies, much appreciated. I have added woo_auto_key to my SQL statement. I am receiving this new error in the sys_error_log table. I have also included my SQL statement below. Goal is to send customer quote statements to individual customers. Previous ERP had this capability. This capability is not standard in Quantum.

“ORA-31011: XML parsing failed

ORA-19202: Error occurred in XML processing

LPX-00229: input source is empty

ORA-06512: at “SYS.XMLTYPE”, line 272

ORA-06512: at line 1″

SQL statement:

SELECT BA_VIEW_WO_SUMMARY.CUSTOMER_PO, BA_VIEW_WO_QUOTE.SENT_DATE AS QUOTED_ON, BA_VIEW_WO_SUMMARY.PN,

BA_VIEW_WO_SUMMARY.DESCRIPTION, BA_VIEW_WO_SUMMARY.SERIAL_NUMBER AS SN, BA_VIEW_WO_QUOTE.WO_NUMBER,

BA_VIEW_WO_QUOTE.WOO_AUTO_KEY, BA_VIEW_WO_QUOTE.QUOTE_AMOUNT AS AMOUNT

FROM BA_VIEW_WO_QUOTE LEFT OUTER JOIN

BA_VIEW_WO_SUMMARY ON BA_VIEW_WO_QUOTE.WO_NUMBER = BA_VIEW_WO_SUMMARY.WO_NUMBER

WHERE (BA_VIEW_WO_QUOTE.SYSCM_AUTO_KEY = ‘3’) AND (BA_VIEW_WO_QUOTE.APPROVED_DATE IS NULL)