If that's the case, it sounds like you could write a script that creates a
custom open dialog ... it would
-- after you select the file you want to open, check to see if there is a
file of the same name with .lck extension ...
-- if yes, not let you open the file;
-- if no, let you open the file and create a .lck file

All developers would then need to ALWAYS use the custom open dialog to open
files.

H.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Owens
Internet Operations Coordinator
Ventura County Star / E.W. Scripps Co.
www.venturacountystar.com
[EMAIL PROTECTED]
AIM: GoCatGo1956
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

> -----Original Message-----
> From: Kevin Graeme [SMTP:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2003 9:12 AM
> To: CF-Talk
> Subject: Re: "lite" source control for Homesite+ ?
>
> > We're on the same network. How does MS Office do it so effortlessly? Do
> > Word and Excel have a built-in CVS system?! Or is there just a bit of
> > Windows scripting that can replicate this? The more I look at it, the
> more
> > it seems odd that this basic little idea isn't built into Windows
> > drive/file sharing.
>
> Office does it in pretty much the same way that DW does it. When you open
> the file, it puts a .lck file there with the same name. Then when anyone
> else tries to open the file, Office looks for a file of the same name but
> with a .lck extension. If that exists, then it warns the user.
>
> -Kevin
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to