*cabe logging?

[Bob Stockler]

Tim Fischer wrote (on Tue, Jun 14, 2005 at 10:57:42AM -0400):

| We're having some really strange issues this morning where code that we 
| put in will be missing mere minutes later.  I have no idea how this is 
| happening, but I'm wondering if someone is leaving a *cabe window open 
| then saving and overwriting changes that had been made.
| 
| Is there a way to log when someone opens *cabe and when they save it?  
| Is there anyway to activate some kind of "checkout" policy with *cabe so 
| that no 2 people can edit the same processing table?  If no to 
| both/either of these, is this a planned addition?

There's no locking of a processing table while it's being
edited with *cabe.

You could write a filePro input processing table with an
@MENU routine that presented a processing table menu similar
to the one in *cabe, and use a LISTBOX to show the available
tables if choice 3 was elected.

On a table being selected a lockfile, in perhaps the style
"tablename.lck" and maybe holding the users name, would be
written in the filePro file directory containing the table.

Then use a SYSTEM command to execute the cabe editor.

On a user selecting a table to edit, a check would be made
to see if there was a lockfile on it, and deny the request
if it had one, while showing who had it open.

Or, you could arrange better communications between those who
have access to the development system programs.

Bob

-- 
Bob Stockler - bob at trebor.iglou.com - http://members.iglou.com/trebor
Author: MENU EDIT II - The BEST Creator/Editor/Manager for filePro User Menus.
Fully functional (time-limited) demos available by email request (specify OS).