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!
|
|
message, Remote client
Posted: 31 Jan 08 12:38 PM
|
Hello,
I have installed a remote user and the configuration of the synchronization is:
Automatic Sync: On
Sync runs when you first connect and then every or 1 Hours and minutes.
The requirement is that the timing is every minute. All this works properly.
The problem I have is that when you configure your client synch every minute on the remote client I deploys the following message:
"Sync client has successfully applied transactions to your local database. Do you want to refresh the client now?"
This message I displayed that the main database is constantly changing.
My question is how can I make the message does not display the remote user?
If the message is displayed every minute is something ugly for the remote user.
One suggestion is to synchronize every 15 minutes, but my requerimieto is to synchronize every minute.
Does anyone have any suggestions or comments?
|
|
|
|
Re: message, Remote client
Posted: 31 Jan 08 5:31 PM
|
Having a remote user sync every minute is unworkable. Can you explain why this is necessary?
What happens when there is a lot of data to transfer and the user has a slow connection? Sync will take considerably more than 1 minute in this case.
If the data needs to be that up to date, the user should be accessing the host database directly: either over the network, via Citrix/Term Services or (very) fast VPN connection.
The sync client updates the client database in the background. Performing a refresh of the SLX client data is the only way to see the updated data, so this must happen after a sync and, as far as I know, cannot be made automatic.
Phil |
|
|
|
Re: message, Remote client
Posted: 31 Jan 08 6:10 PM
|
Hello Phil Parkin,
The remote user has two ways of working:
1) The remote user works 8 to 12 hours outside the office, where it is necessary to take the remote database. This schedule is very useful and necessary to install the remote client. The remote user is not connected to the corporate network.
2) The remote user works 13 to 18 hours in the office, at that time the remote user is connected to the corporate network. Here is where we have the problem. In the 13 hours to 18 hours requires that the database user remote sync every minute or every 5 minutes maximum. And the problem is that every 5 minutes, the remote user will see the message updating data.
What state seeking to solve the problem is that this message does not unfold, but I have not been able to solve the problem.
Any suggestions for this problem?
|
|
|
|
Re: message, Remote client
Posted: 31 Jan 08 6:13 PM
|
OK, it's easy. Create another connection for the remote user - directly to the host database.
Then teach them to use that connection while they are in the office and to use the remote connection while they are not. Hopefully this is not a stupid salesperson and they will grasp the concepts involved 
Phil |
|
|
|
Re: message, Remote client
Posted: 31 Jan 08 6:17 PM
|
| Thanks for your help and suggestions, I will raise your recommendation on the company. I hope that the company can understand the concepts of remote user. |
|
|
|
Re: message, Remote client
Posted: 31 Jan 08 6:18 PM
|
In case they are a stupid user  , it would be a simple task to create a small launcher app for them. Something that allowed them to enter their username & password and then select either "I am in the office' or "I am away from the office" option. Then the launcher app would just kick off SLX on the command line and pass the username, password, and the appropriate connection name for them (See http://saleslogixblog.com/rfarley/archive/2006/12/04/36835.aspx for command-line options)
This way the launcher app would be reusable for other users as well (assuming you named their connections the same)
-Ryan |
|
|
|
Re: message, Remote client
Posted: 01 Feb 08 9:32 AM
|
This works technically on the assumption that "connected to the corporate network" does in fact mean a Local area network connection and not a WAN connection. We still do not recommend using SalesLogix rich Client over a WAN link.
The one area to watch out for with this approach is that the user will b e tempted to close their computer and leave the office without doing a final sync at the end of the day and/or they may work off line on their remote overnight but not sync before going back to the office. In these cases, they will log in to the Host (or their Remote) and find data not matching how they left it andlose confidence in the system or duplicate transactions before sync catches up a few minutes later.
Make sure that they are taught to always sync first thing when connecting and last thing before disconnecting and why this is important. Leave thier AutoSync on and set to the minimum practical settng of 15 minutes so their system is stayong current within that amount throughout the day. (Just have them open the Sync Client from the AutoSync icon in the tray when they first connect or before they disconnect to run it manually) |
|
|
|
Re: message, Remote client
Posted: 01 Feb 08 4:57 PM
|
Originally posted by Bryan
Hello,
....
One suggestion is to synchronize every 15 minutes, but my requerimieto is to synchronize every minute.
...
|
|
FYI - it does NO good to synnch at a high frequency sinc it means nothing.. If the main sync server is running every 15 minutes the remote changes are not seen in the main db (or the other way around) except for every 15 minutes.
Remember.. a remote sync is NOT with the actual main db.. just the "buckets" holding changes to/from the main. There is no direct coupling.. If there were.. it would be a direct connect.. we call that a LAN client  .. as others have already pointed out..
--
RJLedger - rjlSystems |
|
|
|
Re: message, Remote client
Posted: 01 Feb 08 5:08 PM
|
Thanks for the comments and segerencias.
His comments were helpful to identify remote users and their way of connection, and be able to explain to the heads of the company.
Thanks |
|
|
|