To answer your question, if you try to open the table exclusively and you can't, you will get a trapable error. If you trap this error, you know that other's are using the table.

Were you really going to use ZAP? I would think that if a table is going to be ZAPped with any frequency, it might be an idea to make it a local table (on each client) to speed things up. I am assuming a few things, but a table that is ZAPped is usually a temporary table (ie. the data in the table is not going to be kept in that table for a long period of time). You might want to give more information and/or re-think your design in the area of your system.

As far as actually using commands like PACK where exclusive use is needed in the system: I have a few utilities in our system that can be run from the file server. One of these utilities takes a path and PACKs all the databases and tables and re-indexes. I use the SYS(2000) function for this one to get all the DBCs and DBFs. But this type of thing is only used periodically as we don't usually have deleted records kicking around. A few tables that don't recycle deleted records might get them as I do manual "fixes" over time. But I don't think this type of thing should be done very often and I really don't think it should be done at times when other users may have to wait to use the system.

Anyways, good luck.

Joe



>Starting first attempt at multi-user.
>
>Is there a function available to determine if other users are sharing a table in a multi-user environment?
>
>I would assume one should first check if the table is opened by other users prior to performing certain table functions, ie; zap
>
>Any assitance would be appreciated.