---

laurie_lynne wrote:

This issue came up before, but it's turned into a problem...

 

We're using TS2009 (my computer) and TSRemote Plus in a small office.  One of my attorneys added a client to his Remote TS, and I had a bunch of problems with it, so I CLOSED the bad one and created a new one on my computer.  The Nickname1's are almost, but not quite, identical.  The problem is that now when we exchange databases, I'm NOT getting the slips for this client, and the attorney keeps NOT getting the client data loaded into his database.

 

So, two questions:

 

1.) What's going on?   (I would have figured that the NEW version of the client would have some internal ID number or something that would just "go" to the remote without question, but now I'm curious about how it works and why what I did isn't working.)

 

2.) How do I fix it?  (i.e., get the new client into the Remote TS database and get his slips into mine)

 

-laurie

---

I've been trying to stay out of this one because I am not a fan of the exchange database function and remotes.  It always seems to eventually lead to something like this, or slips coming in scrambled, or whatever.

What I have my remote using firms do is 1) create the initial transfer database to seed the TSRemote with some clients, timekeepers, activities, etc. and have my remote user enter his/her time, but then when it comes time for the return trip, I have them use the Archive function in the Remote to spit out a TSF (Timeslips format) file with the new slips in it (choosing the option to mark them as Exported when they send them).  They then transfer it back to the central billing computer and use the Combine function (specialized form of TSImport) to bring those slips into the main Timeslips database.  If there are any issues bringing them in TSImport will prompt me for what to do about it, and note any anomilies in the Journal.

New clients are entered into the main computer as usual.  The remotes can be updated with the new clients either A) with a periodic new TSF file (but beware, getting a new one will replace the one the remote has with slips in it, and they will start anew with a blank slate), or B) just let the remote users put a nickname themselves to track time on (all you need to make a slip is a nickname) and when they produce the archive, use a filter of not yet exported.  If the remote users happens to put in a different nickname than central did, you will catch it on the import and can either have the remote edit their nickname to match central, or create a translation in the import template that essentially says "Every time George sends an archive file with a slip for Hany, match that slip up with the central billing computer's client Haney).  You can also do a combination of both, say giving them new TSF files every 6 months to keep them more or less in synch.

Clear as mud?

Hope this helps.  If you think this suggestion was especially helpful, please consider clicking the KUDOS! (yellow) icon in this message.  Thanks.

Nancy Duhon, Esq.
Certified Consultant for Timeslips and Amicus Attorney
Duhon Technology Solutions, LLC
[email protected]
404-325-9779
Providing personalized local and remote online support for Timeslips users for over 15 years. 

---

laurie_lynne wrote:

This issue came up before, but it's turned into a problem...

 

We're using TS2009 (my computer) and TSRemote Plus in a small office.  One of my attorneys added a client to his Remote TS, and I had a bunch of problems with it, so I CLOSED the bad one and created a new one on my computer.  The Nickname1's are almost, but not quite, identical.  The problem is that now when we exchange databases, I'm NOT getting the slips for this client, and the attorney keeps NOT getting the client data loaded into his database.

 

So, two questions:

 

1.) What's going on?   (I would have figured that the NEW version of the client would have some internal ID number or something that would just "go" to the remote without question, but now I'm curious about how it works and why what I did isn't working.)

 

2.) How do I fix it?  (i.e., get the new client into the Remote TS database and get his slips into mine)

 

-laurie

---

I've been trying to stay out of this one because I am not a fan of the exchange database function and remotes.  It always seems to eventually lead to something like this, or slips coming in scrambled, or whatever.

What I have my remote using firms do is 1) create the initial transfer database to seed the TSRemote with some clients, timekeepers, activities, etc. and have my remote user enter his/her time, but then when it comes time for the return trip, I have them use the Archive function in the Remote to spit out a TSF (Timeslips format) file with the new slips in it (choosing the option to mark them as Exported when they send them).  They then transfer it back to the central billing computer and use the Combine function (specialized form of TSImport) to bring those slips into the main Timeslips database.  If there are any issues bringing them in TSImport will prompt me for what to do about it, and note any anomilies in the Journal.

New clients are entered into the main computer as usual.  The remotes can be updated with the new clients either A) with a periodic new TSF file (but beware, getting a new one will replace the one the remote has with slips in it, and they will start anew with a blank slate), or B) just let the remote users put a nickname themselves to track time on (all you need to make a slip is a nickname) and when they produce the archive, use a filter of not yet exported.  If the remote users happens to put in a different nickname than central did, you will catch it on the import and can either have the remote edit their nickname to match central, or create a translation in the import template that essentially says "Every time George sends an archive file with a slip for Hany, match that slip up with the central billing computer's client Haney).  You can also do a combination of both, say giving them new TSF files every 6 months to keep them more or less in synch.

Clear as mud?

Hope this helps.  If you think this suggestion was especially helpful, please consider clicking the KUDOS! (yellow) icon in this message.  Thanks.

Nancy Duhon, Esq.
Certified Consultant for Timeslips and Amicus Attorney
Duhon Technology Solutions, LLC
[email protected]
404-325-9779
Providing personalized local and remote online support for Timeslips users for over 15 years.