>Hello John.
>
>The machine is actually a shrimp classification machine, each user has to input more
>data than I've showed and they recieve a paper with the information on it.
>
>Right now whe have 5 machines and the probability of a mistake has increased a lot.
>
>I was thinking about the lock procedure, but is that possible in MS Sql Server ?

Transactionally, yes! But I think I need a better understanding of your business and application models to know for sure. Email me; glad to help.

>I'm sure I read somewhere something about that, but I can't remember where.
>
>Another alternative is to run a batch process to verify data consistency each day
>or twice a day.
>
>c.x.
>
>>Hey Carlos,
>>
>>Consider changing the machine ID from being a user input to a programmed entry using SYS(0). If you can't do that, surely you can use old-fashioned locking to lock the base table on Save and do a query for entires for that machine for conflicting time period as Alex mentioned?
>>
>