Login / Register  search  syndication  about

          Ryan Farley's Blog

Ryan Farley on .NET Development with a focus on CRM Development for SalesLogix

ADO CursorLocation and SalesLogix

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.

What's This?
  
Bookmark and Share

About Ryan Farley

   Ryan Farley is the Director of Development for Customer FX and creator of slxdeveloper.com. He's been blogging regularly about SalesLogix since 2001 and believes in sharing with the community. He loves C#, Javascript, Python, web development, open source, and Linux. He also loves his hobby as an amateur filmmaker.

View the SalesLogix Mobile Seveloper Series
View the SalesLogix SData Developer Series
View the Git for the SalesLogix Developer series



Related Content
   Using a Test Plan
So you have approved the Statement of Work (SOW) for some modifications and are awaiting the delivery of
Posted on Mar 13, 2014 by George Jensen to George Jensen's Blog
 
   Creating a Saleslogix Ticket Pretty Prefix and Suffix in External Applications
Some entities in SalesLogix, such as Tickets, use a "pretty key" as an easier to use value to r
Posted on Feb 28, 2014 by Ryan Farley to Ryan Farley's Blog
 
   Evaluating strings in C# Code snippets
When checking for two (or more) different values for a property in a code snippet, you can't simply l
Posted on Dec 13, 2013 by Jason Buss to Jason Buss' Blog
 
   Updates to the SalesLogix Mobile Developer Toolkit
I've released some updates to the SalesLogix Mobile Developer Toolkit. This new release adds some fix
Posted on Apr 10, 2013 by Ryan Farley to Ryan Farley's Blog
 
   Free Tool to Retrieve SalesLogix User Names and Passwords
As a business partner we work with customer SalesLogix databases often. Along with getting a database bac
Posted on Feb 25, 2013 by Ryan Farley to Ryan Farley's Blog
 
Comments

 

Jeremy Brayton said:

Thanks for saving my butt. You taught me on slxdeveloper.com how to use updatable recordsets and this was one of the requirements of using that.

Does the provider default to client side now? Or do we have to explictely call this. My guess would be no, that it ADO recordsets default to server side and they can't be altered. The alternative is to explicitely call this every time you want to access data, whether its a read or a write. I relied on defaults to let me read data not expecting I would have to change those eventually but I suppose it's inevitable and should be changed anyways.
September 27, 2004 10:25 AM

Leave a Comment

(required)  
(optional)
(required)  
Add
All contents Copyright © 2014 Customer FX Corporation
Customer FX Corporation
2324 University Avenue West, Suite 115
Saint Paul, Minnesota 55114
Tel: 800.728.5783

  Follow @CustomerFX on twitter
Follow the best news, tips, and articles
  Subscribe to Customer FX on youtube
Watch SalesLogix tutorial videos from Customer FX
Login / Register