>>It is the 'You can't log in right now...' portion that is the problem. The user needs to log in 100% of the time. So I can put it in a loop, but what I want to make sure of is that they get logged in. How about:
>>
>>DO WHILE NOT rlock('0','mytable')
>> insert into mytable values (value1, value2)
>> unlock record 0 in mytable
>> EXIT
>>ENDDO
>
>This is probably vague enough that some people will bitch at me posting it, but what the hell, it might help.
>
>Anyway, I remember there being something like "set retry" that would tell VFP how many times to try and get a lock before giving up. So, couldn't you use that to try a few times to get the lock so the person could log in and if it wasn't successful, then you know something's wrong because it shouldn't be locked that long...
>
>Michelle
I will be useing the SET REPROCESS in conjunction with the FLOCK()/UNLOCK strategy. Thanks for your response.
Bret Hobbs
"We'd have been called juvenile delinquents only our neighborhood couldn't afford a sociologist." Bob Hope