YES, This was it!! - You are absolutely correct.

I had not consider that another station CLOCK may not be in Sync.
So, I changed the prompt read "Please verify System Clock is in Sync on all stations).

Thanks everybody for your inputs. This is indeed a great forum.
Cyrus


>>I use Time Stamps in my App and have a Function that retrieves unique Time Stamps.
>>
>>I have a sitation with one system (so far) that is returning the "The system clock seems to be stuck" message in the code below.
>>How is this even possible ?! - And if something wierd is actually causing it, how can it be fixed ?
>>
>>
>>

>>
>>* MFS_TRAN.TRANS_ID - Contains the last DATETIME() value from the previous call.
>>
>>ngCount = 0
>>timeStamp = DATETIME() 
>>IF timeStamp > MFS_TRAN.TRANS_ID 
>>   * we're home!
>>ELSE   
>>   * This case should only happen if last call was less than a seconds ago.
>>   DO WHILE timeStamp <= MFS_TRAN.TRANS_ID
>>      ngCount = ngCount + 1
>>      WAIT '' TIMEOUT 1  
>>      timeStamp = DATETIME()  && By this 1 second delay, we MUST get a fresh Time Stamp 
>>      * but lets check it anyway. 
>>      IF timeSTamp <= MFS_TRAN.TRANS_ID .AND. ngCount > 10  && we have looped 10 times with 1 second delay. 
>>
>>         WAIT '-- The system Clock seems to be stuck....' + CR + ;
>>              '      (press any key to continue)'  WINDOW  TIMEOUT 5
>>
>>         EXIT  && Send your best time stamp.
>>      ENDIF  
>>   ENDDO
>>ENDIF   
>>REPLACE MFS_TRAN.TRANS_ID WITH timeStamp
>>RETURN timeSTamp
>>
>>

>
>First the obvious question : Is the MFS_TRAN.TRANS_ID value used by different machines ?
>If not then is the machine in question configured to automatically re-sync with a time server ?