this behavior ... using, say the OpenTextFile method, and setting the iomode
to "ForWriting" or "ForAppending"? Since the file was open in a way that
told the system it was going to be written to, if that wouldn't lock it for
any other application.
If such operations are part of the API, I've got to believer there is a way
to get to that function through ADO.
H.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Owens
Internet Operations Coordinator
Ventura County Star / E.W. Scripps Co.
www.venturacountystar.com
[EMAIL PROTECTED]
AIM: GoCatGo1956
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> -----Original Message-----
> From: Samuel Neff [SMTP:[EMAIL PROTECTED]
> Sent: Wednesday, October 15, 2003 8:44 AM
> To: CF-Talk
> Subject: RE: "lite" source control for Homesite+ ?
>
> This functionality is built into Windows, it just depends on how
> applications implement file open/save.
>
> In Windows API you can open a file, read to it, and optionally close it.
> Multiple program can get a shared open of a file or programs can get an
> exclusive open of a file. If you do an exclusive open and leave it open,
> then the file is locked and windows won't let another program open it.
> This
> is how Office does it's file open/save. It even allows the program to be
> notified when the file is no longer locked, which is a very kewl feature
> not
> present in most source control systems. However, most text editors,
> including HomeSite, open a file, read to memory, and then close it. When
> the save, then open, write, and close. They don't leave it open and thus
> it
> can be modified by another program. AFAIK, there is no option to change
> this behavior.
>
> Sam
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
