What do you mean by "keep track of it"??

When a user want's to edit a record you check if the field is set. If not, then set it and allow...

So you have debugging code in your production stored procedures ?

Well that's another issue ...

How about the tried and tested method of passing...

If your column is defined as char(5), then the data is actually going to be

'9876 ' or '1647 ' ** note trailing blanks

SQL automatically pads out CHAR fields...

The query you're using will not work. I don't know what your front-end is or how it displays the data to users. The usual method would be for the front-end...

???

Do you want to interrogate SQL Server to determine the locking, or do you have a seperate field that indicates if the record is locked or not? If you have...

In your initial example you just executed the xp_cmdshell procedure but didn't store it anywhere. If you replace that with my suggestion then the results are stored in the temp...

Have you checked the event logs on the server and client?

Most likely culprit is network connectivity. Are there any configuration options in the client that allow you to increase time...

You'll need to insert the results from xp_cmdshell into a temp table.

EG:

Create table #xp ( xp_out varchar(255) )

INSERT INTO #XP

EXEC Xp_cmdshell etc...

If you type sp_help 'UsersRoles' into Query analyzer you should be able to see who owns the table. If you can't change the owner, the just user the...

Where are you viewing the list of tables from?

The UsersRoles table is probably not owned by dbo. You can use sp_changeobjectowner to change it to dbo if need be.

In terms of SQL Server capacity I don't see any problems with the number of records and database objects. It may seem a lot when you look at it from...

Is "UsersRoles" the right name for the table?

Some good books I've got are,

With an ASP.Net and Database focus

 - Building Web Solutions with ASP.NET and ADO.NET

 - Beginning ASP.NET 1.1 with Visual...

I don't have access to my Report Server at the moment, but isn't there  userid property you can use?

Hmmm ... it may be because you'll need a BEGIN and END around the ELSE part of the IF statement. Without the BEGIN ... END, it would execute the SET...

Egads, yet another thread.

Refer to my last post over here,

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=163086

If you don't understand my suggestion, post a reply explaining what you don't understand.