I see the question arise often about CursorLocation with Recordsets in SalesLogix. This question comes up even more now with SalesLogix 6.2 as neglecting to set CursorLocation can have have more noticable results.
Any data access using the SalesLogix OLEDB Provider must use a client-side cursor. Server side cursors are not supported. In SalesLogix 6.2 you will not even be able to access data without specifying a client side cursor. Previous versions would let you get away with omitting the CursorLocation (ie: defaulting to serverside) and retrieve data, although you would receive an error when updating without a client-side cursor. In 6.2 you are no longer able to access data without specifying a client-side cursor.
With traditional ADO in a SalesLogix VBScript, you must use the following:
objRS.CursorLocation = adUseClient
Even if you’re not yet on version 6.2 you should be using a client-side cursor anyway. The provider is not built to handle server-side cursors, and you’re code will break when you move it to 6.2.