Steve,

Thank you for your efforts, but I regret to inform you that the information provided is incorrect, and my question remains unanswered.

I'm not browsing the record using move methods. Those particular lines are commented out see above code

With the current code edit line method doesn't add anything.

This line > wrtVal = oSOHdr.oLines.nWrite() '<Error #12

EditLine() is doing a SetKey().  If the LineKey$ doesn't exist it WILL create a new line and return the 2 which indicates a new record.

If the value for LineKey$ is blank it will create a new line, returning the 2 which indicates a new record.

Yes, I am indeed aware of the details you mentioned. As previously stated in the script snippet and shown in the provided screenshot, the LineKey$ is passed to the SetValue method using the variable sLineKey. I have thoroughly checked and confirmed the spelling and data types. The return value of edtLne indicates whether it pertains to a new line or an existing one. In this particular case, the expected return value should be 1, correct?

I have executed the script in the Purchase Order (PO) module, and I have observed the same behavior persisting.

It is important to note that the client is currently operating Sage2022 with ScanCo PM and MultiBin functionalities, and no JC (Job Costing) directories or modules have been installed.

Considering this new J/C error (RA error above fixed), I have taken the initiative to request the reseller to open a case with Sage. It is possible that this error is the cause of the incorrect return values we have been discussing.

Based on these observations, I strongly believe that this issue is an oversight among the programming team during the unit testing phase.

Regards,

SKG

	'
	'*	###  S E T   S O   P R O G R A M   ###
	'
	Dim setProgram As Variant
	'*
	setProgram = 0
	setProgram = oSS.nSetProgram(oSS.nLookupTask("SO_SalesOrder_UI"))
	If setProgram = 0 Then : MsgBox("ERROR: " & oSS.sLastErrorMsg) : Else  MsgBox("Set Program Good") '< Debug Msg
	If setProgram <> 0 Then
		Set oSOHdr = oScript.NewObject("SO_SalesOrder_BUS", oSS )
		Set oSODtl = oScript.NewObject("SO_SalesOrderDetail_BUS", oSS )
		'
		'*	### I T E R A T E   MS  t b l S A L E S D t l
		'
		'*	Select sage values from sales detail table
		sSQL = ( "SELECT SalesOrderNo, LineKey, UDF_PMQTY, Approve FROM tblSalesDtl WHERE Approve = -1 Order By SalesOrderNo ASC" )
		Set rst = CurrentDb.OpenRecordSet( sSQL )
		If rst.RecordCount <> 0 Then
			rst.MoveFirst
			Do While Not cBool( rst.EOF )
				'
				sSONo = Nz( rst.Fields( "SalesOrderNo" ).Value ,"" )
				sLineKey = Nz( rst.Fields( "LineKey").Value, "" )
				bApprove = Nz( rst.Fields( "Approve" ).Value, 0 )
				If bApprove = -1 Then :	bSMI = "Y" : Else bSMI = "N"
				'
				'*	### F I N D   S A L E S O R D E R   ###
				'*	
				setVal = oSOHdr.nSetKeyValue( "SalesOrderNo$", sSONo )
				fndVal = oSOHdr.nFind()
				'
				'*	### S E T   K E Y ###
				'
				If fndVal <> 0 Then
					setVal = oSOHdr.nSetKeyValue( "SalesOrderNo$", sSONo )
					setKey = oSOHdr.nSetKey()
					If setKey <> 0 Then 
						setVal = oSOHdr.nSetValue( "UDF_SMI_RELEASE$", bSMI ) '< set scan date
						'
						'movVal = oSOHdr.oLines.MoveFirst() '< RunTime error# 438 Object doesn't support this property or method
						'Do While Not cBool( oSOHdr.oLines ) '< Error see above
							'
							edtLne = oSOHdr.oLines.nEditline( sLineKey ) 
							setVal = oSOHdr.oLines.nSetValue( "UDF_PMQTY", nPMQty )
							wrtVal = oSOHdr.oLines.nWrite() '<Error Module J/C is not on file
							'
							'movVal = oSOHdr.oLines.MoveNext() '< Error see above
							'
						'Loop '<Error
						'
						wrtVal = oSOHdr.nWrite()
					End If
					MsgBox("SO Completed") '< Debug Msg
				End If
				rst.MoveNext
			Loop
		End If
	End If
	retVal = oSS.nCleanup()
	retVal = oSS.nLogoffUser()
	'
	Debug.Print "END btnSageDtl_Click"

After your SetKey for oSOHdr, you need to create your lines object from the already-open header... Ex. oSOLines.

Set oSOLines = oSession.AsObject(oSOHdr.Lines)

...then you should be able to navigate the orders lines.

movVal = oSOLines.MoveFirst()

For a lines object, the edit key is not just the LineKey value.

sSurchargeEditKey = oLines.GetKey()

. . .

retVal = oLines.EditLine(sSurchargeEditKey)

Dear Kevin M,

I sincerely appreciate the time you've taken to assist me. However, despite your efforts, I'm still encountering the RT error# 438, which states, "Object doesn't support this property or method."

Please note that the script is being executed from a Microsoft Access module. Modified script below.

Thank you once again for your support.

Best regards,

SKG

	'*	###  S E T   S O   P R O G R A M   ###
	'
	Dim setProgram As Variant
	'*
	setProgram = 0
	setProgram = oSS.nSetProgram(oSS.nLookupTask("SO_SalesOrder_UI"))
	If setProgram = 0 Then : MsgBox("ERROR: " & oSS.sLastErrorMsg) : Else  MsgBox("Set Program Good") '< Debug Msg
	If setProgram <> 0 Then
		Set oSOHdr = oScript.NewObject("SO_SalesOrder_BUS", oSS )
		'Set oSODtl = oScript.NewObject("SO_SalesOrderDetail_BUS", oSS )
		'
		'*	### I T E R A T E   MS  t b l S A L E S D t l
		'
		'*	Select sage values from sales detail table
		sSQL = ( "SELECT SalesOrderNo, LineKey, UDF_PMQTY, Approve FROM tblSalesDtl WHERE Approve = -1 Order By SalesOrderNo ASC" )
		Set rst = CurrentDb.OpenRecordSet( sSQL )
		If rst.RecordCount <> 0 Then
			rst.MoveFirst
			Do While Not cBool( rst.EOF )
				'
				sSONo = Nz( rst.Fields( "SalesOrderNo" ).Value ,"" )
				sLineKey = Nz( rst.Fields( "LineKey").Value, "" )
				bApprove = Nz( rst.Fields( "Approve" ).Value, 0 )
				If bApprove = -1 Then :	bSMI = "Y" : Else bSMI = "N"
				'
				'*	### F I N D   S A L E S O R D E R   ###
				'*	
				setVal = oSOHdr.nSetKeyValue( "SalesOrderNo$", sSONo )
				fndVal = oSOHdr.nFind()
				'
				'*	### S E T   K E Y ###
				'
				If fndVal <> 0 Then
					setVal = oSOHdr.nSetKeyValue( "SalesOrderNo$", sSONo )
					setKey = oSOHdr.nSetKey()
					If setKey <> 0 Then 
						'
						'Set oSOLines = oSS.AsObject( oSOHdr.Lines ) '< ERROR RunTime error# 438 Object doesn't support this property or method 
						'
						setVal = oSOHdr.nSetValue( "UDF_SMI_RELEASE$", bSMI ) '< set scan date
						'
						'movVal = oSOLines.MoveFirst() '< RunTime error# 438 Object doesn't support this property or method
						'Do While Not cBool( oSOLines ) '< Error see above
							'
							getLineKey = oSOLines.GetKey()
							MsgBox("getLineKey: " & getLineKey ) '< Debug Msg
							'
							edtLne = oSOLines.nEditline( sSONo & sLineKey ) 
							setVal = oSOLines.nSetValue( "UDF_PMQTY", nPMQty )
							wrtVal = oSOLines.nWrite() '<Error Module J/C is not on file
							'
							'movVal = oSOLines.MoveNext() '< Error see above
							'
						'Loop '<Error
						'
						wrtVal = oSOHdr.nWrite()
					End If
					MsgBox("SO Completed") '< Debug Msg
				End If
				rst.MoveNext
			Loop
		End If
	End If
	retVal = oSS.nCleanup()
	retVal = oSS.nLogoffUser()

Steve,

I hope this message finds you well. Since 1993, I have witnessed the remarkable growth of this product, and even now, I am driven to enhance its usefulness and contribute towards improving the overall user experience.

I want to express my sincere appreciation for your decision to contribute your time and expertise in the likeness.

Your commitment is truly valued and makes a significant impact.

I am committed to continue this research journey to discover a solution that aligns with the customer's desired functionality for the UI.

I will persevere in my efforts to find the appropriate resolution.

Best Regards,

SKG

In VBA BOI scripting, and BOI in general object properties begin with a letter that identifies type. "o" is for object and while ".lines"  works in event scripting or UDS's, ".oLines" is used in BOI. I also don't use the method AsObject to get a lines object I use:

Set oSOLines = oSOHdr.oLines

This is how I was taught in BOI class 25 years ago: Set oGLJournalLines = oGLJournalEntry.oLines

I don't do external scripting, just UDS run from within Sage business objects.  That is the syntax I use... but of course, some syntax details for external scripts are different, as you know.

I don't do external scripting, just UDS run from within Sage business objects.  That is the syntax I use... but of course, some syntax details for external scripts are different, as you know.