main logo
Subject: Re: FAQ: Difference between VBlob.SetBlank and VBlob.DeleteData
Author: Ruslan Zasukhin
Posted: 2001/12/29 11:08:37
 
View Entire Thread
New Search


on 12/29/01 17:40, Francois Van Lerberghe at fvanlerberghe (at) freegates .D.O.T be
wrote:

>> VBlob.SetBlank -- just clear RAM buffer of field to prepare it for new
>> record.
>> Usually after this must follow Set BLOB value and AddRecord().
>>
>>
>> VBlob.DeleteData -- delete existed BLOB data of CURRENT record.
>> You fix this deletion by Table.UpdateRecord() or Cursor.UpdateRecord().
>
> Thus, if I write
>
> myCursor.myVBlob.SetBlank
> my Cursor.UpdateRecord()
>
> the (existing) BLOB is "de-assigned" to the current record but not
> deleted ?

I am afraid yes.

I also think that this can be dangerous.
May be better in future make that

myCursor.myVBlob.SetBlank
my Cursor.UpdateRecord()

Work as

myCursor.myVBlob. DeleteData
my Cursor.UpdateRecord()


--
Best regards,
Ruslan Zasukhin

-------------------------
Paradigma.

e-mail: ruslan@paradigmasoft.com
web : http://www.paradigmasoft.com

To subscribe to the Valentina mail list
send a letter to valentina-on (at) lists .D.O.T macserve.net
 
©2001 Ruslan Zasukhin
<-- Prior Message New Search Next Message -->