Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Thursday, May 16, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 External Development Forums - SalesLogix OLEDB Provider
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix OLEDB Provider | New ThreadView:  Search:  
 Author  Thread: Is Parameter Re-Use Supported?
Dean Kier
Posts: 1
 
Is Parameter Re-Use Supported?Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 01 Sep 06 3:25 PM
fiogf49gjkf0d
Hello from a lazy SQL developer. I've grown addicted to the parameter re-use in MS SQL Server like

Update Account Set Account = Account + @param where Account > @param
(Stupid query I know, but it uses the same param twice)
Instead of
Update Account Set Account = Account + ? where Account > ?
(2 seperate parameters)

Is there any way to pull this off(specifically in .net 2.0) through the provider? Now if I want to do a fairly substantial update query or some quick and dirty rendition of optimistic concurrency I end up with enough ? in the query to go batty before I get the parameters all set.

Thanks,
Dean
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/16/2024 5:31:04 PM