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!
|
|
Run SLX script on a nightly basis..
Posted: 14 Sep 07 8:54 AM
|
I have an slx script that updates a bunch of totals nightly. I was planning on running it as an agent each night, but it is failing when autosync occurs. I have run the script from within SLX with no problems.
Is there an alternative way to run an slx script nightly other than with an agent? It is it possible to call slx scripts from KS? Thanks |
|
|
|
Re: Run SLX script on a nightly basis..
Posted: 14 Sep 07 10:23 AM
|
Steve, Does you script make any call to things that live in the SalesLogix.exe? Things like Application.Basic... If so it will fail because the SalesLogix.exe is not in memory. Could this be what is happening?
|
|
|
|
Re: Run SLX script on a nightly basis..
Posted: 17 Sep 07 2:52 AM
|
I don't know about running them directly within SLX, but I use Scribe Insight (www.scribesoft.com). I use it to do batch scripts on a scheduled basis. Even better is that it can then pump that data out to other systems automatically. |
|
|
|
Re: Run SLX script on a nightly basis..
Posted: 18 Sep 07 6:57 AM
|
Originally posted by Steve Knowles
I have an slx script that updates a bunch of totals nightly. I was planning on running it as an agent each night, but it is failing when autosync occurs. I have run the script from within SLX with no problems.
Is there an alternative way to run an slx script nightly other than with an agent? It is it possible to call slx scripts from KS? Thanks |
|
Sure.. it's called Windows Task Scheduler... -- rjl |
|
|
| |
|
Re: Run SLX script on a nightly basis..
Posted: 18 Sep 07 10:49 AM
|
Originally posted by Phil Parkin
Or a scheduled SQL Agent job running a DTS/SSIS package.
You just don't have access to the Application object. |
|
This is the route I would suggest. There is a lot of power there that is fairly easy to use. Not only that, but it is a powerful tool that you already own , (yet so few people seem to take advantage of it). |
|
|
|
Re: Run SLX script on a nightly basis..
Posted: 19 Sep 07 3:45 AM
|
I have had similar problems with Agents in the past. As Ryan Mentioned, DTS/ SSIS is really good for this type of work. Specifically I use it to clear down user created groups over thirty days old, move data from the SalesLogix database to a data mart for Business Objects analyses and a few other odd tasks.
One thing to keep in mind, when using DTS is that unless you make your connections through the SalesLogix provider, your changes won't synch to remotes. I hope that's not trying to teach you to suck eggs, but it bears repeating anyway. Also, if you need to generate SLX ID's in DTS/SSIS there are some good examples on this site in the OLE DB Provider aritcle section.

|
|
|
| |
| |
|
Re: Run SLX script on a nightly basis..
Posted: 19 Sep 07 10:59 AM
|
I would think you could save the script as a .vbs file and then run this with the scheduler. You will most likely have to add a call to the saleslogix object to get it to login and connect but I don't think its rocket science. It would depend on the scripting (my system is 6.2 so its still vbs). |
|
|
|
Re: Run SLX script on a nightly basis..
Posted: 20 Sep 07 7:08 AM
|
Originally posted by Paul Pacun
I would think you could save the script as a .vbs file and then run this with the scheduler. You will most likely have to add a call to the saleslogix object to get it to login and connect but I don't think its rocket science. It would depend on the scripting (my system is 6.2 so its still vbs). |
|
You are correct.. but there's an issue w/trying to use "SalesLogix". Just create a connection to the "provider" and it's just "ADO" after that.
You can create a connection using a .udl file very easily (I think someone's posted about this before.. but in case ...: A - Create a txt file on the desktop B - Change the extension from .txt to .udl C - Double click on it and it will launch the datalink dialog D - Pick the SalesLogix OLEDB Provider E - Fill out the info like you would as if you were connecting up s SalesLogix Client app and save it (w/password) You can refer to this udl in the connection string or just put the contents into a connection string. ex: objConn.ConnectionString = "FileName=\\SLXSrver\SLX\SalesLogix.udl;"
-- rjl |
|
|
| |
|