x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 87 subscribers
  • Views 1344 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
45
topics
91
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
962
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Gerald Cruz

BM ProductionRegister - New object error:200

SUGGESTED
Posted By

Hi,
i've been constantly getting the error "System.Exception: <NewObject Error: 200>" when I register the BM production entries.

here's what I have coded:

                    oSS2.nSetProgram(oSS2.nLookupTask("BM_ProductionRegister_UI"))
                    objTransactionRegister = oScript2.NewObject("BM_ProductionRegister_UPD", oSS2)
                    oSS2.nTerminateUI()
                    If blnUseBatch = True Then
                      retVal = objTransactionRegister.nSelectBatch(strBatchNo)
                    End If
                    retVal = objTransactionRegister.nUpdateInit()
                    retVal = objTransactionRegister.nUpdateMain()
                    retVal = objTransactionRegister.nUpdateCleanup()

                    'drop the Transaction Register
                    objTransactionRegister.DropObject()
                    'drop the session
                    oSS2.DropObject()

Any help/clarification on what I might be doing wrong to register the BM transaction would be greatly appreciated.

Thanks!

Parents
  • 0

    I believe you need a Set at the beginning of line two in your post since you are getting a object handle from the NewObject method. However, you may want to instead consider using the oNewObject or oGetObject methods of your oSS2 object so you can reference its sLastErrorMsg in the event the object could not be created.

Reply
  • 0

    I believe you need a Set at the beginning of line two in your post since you are getting a object handle from the NewObject method. However, you may want to instead consider using the oNewObject or oGetObject methods of your oSS2 object so you can reference its sLastErrorMsg in the event the object could not be created.

Children

*Community Hub is the new name for Sage City