11-26-2013 06:13 AM - edited 11-26-2013 06:16 AM
A - It makes no difference if you use Integration or not - it's "hard-wired" into Saleslogix.
B - Normally I'd yes a remote task to synch out a fix to a remote db (or many remotes). One customer has over 700 ;-) However, it will not work in the case.
I suggest creating a "script" that can be emailed w/instructions to the remotes and having them fire it off. Depending on their rights on their remote (pc) they may or may not be able to run it.
In the past I've created a simple "OSQL" file to do all of this - info here:
If you have not ever created one of these.. I have a sample - contact me directly.
12-17-2013 06:58 AM
Thanks again for everyone's responses. We ended up creating a script which allowed 2 parameters to be entered, the user's site code and the SLX Server name (computer name). I sent individual emails to each remote user with their site code to enter when prompted (the computer name was found by the script).....
So, now that all my remotes are fixed, can I log back into SLX Web and be 100% sure that the systeminfo table will not be changed and sent to the remotes again?
I really don't want to go through this again!
12-17-2013 07:45 AM
The "problem" only happens the first time.. and (AFAIK) it is fixed (design change) in 8.1 (which is in RC now).
01-06-2014 06:11 AM
Thanks - I would like to try and sign in again this morning... is there anything that I can double-check in the systeminfo table to be 100% sure an update won't occur? I'm really very nervous about trying this again. Thanks for all your help.
01-06-2014 08:34 AM
SELECT * FROM sysdba.SYSTEMINFO
Look for avalue in the APPId field - there should be one that looks like a normal SLX Id (12 chars) an probably starting w/a "Q".
If it is there.. you should be just fine.