HLinkMemo (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

This content has been translated automatically. Click here to view the French version.

Help / WLanguage / Managing databases / HFSQL / HFSQL functions

Canceling the existing link
Difference between BinaryLoad and HLinkMemo
HFSQL thumbnails
Managing memos in SQLite

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

HLinkMemo (Function)

In french: HAttacheMémo

Not available with this kind of connection

Used to associate a file with a binary memo item or to cancel the existing link between a file and a binary item.

The file will be read and added to the memo only when the record is added or modified (HAdd, HModify or HWrite). The function will return an error if the file is opened in write mode and if the hAcceptOpenedFile constant was not used.

HExtractMemo will be used to extract the file contained in the memo onto the hard disk.

Note: Direct assignment is also possible:

To associate an image (found in an Image control) with an image memo:
<FileName>.<NameMemoItem> = <NameImageControl>

For example:
```
AFile.AMemoItem = IMG_AnImageControl
```
This syntax can be used with both the HFSQL engine and Native Connectors.
<FileName>.<NameMemoItem> = <BufferName>

For example:
```
bufFile is Buffer = fLoadBuffer("MyFile")
MyFile.MyMemo = bufFile
```

Example

See additional examples

// Attach an image to the record
HLinkMemo(Product, Product_Image, "C:\Images\Product1.gif", hMemoImg)
// Transfer the contents of the controls to the file buffer
ScreenToFile()
// Add the record
HAdd(Product)

Syntax

Associating a file with a binary memo item Hide the details

<Result> = HLinkMemo(<Data file> , <Item> [, <File to attach> [, <Type> [, <Information>]]])

<Result>: Boolean

True if the operation was performed,
False if a problem occurs. HError is used to identify the error. The function will return an error if the file to associate is opened in write mode and if the hAcceptOpenedFile constant was not used.

<Data file>: Character string

Name of the data file (or query) containing a memo item.
If only <Data file> and <Item> are specified, HLinkMemo cancels the existing link between the binary file and the item.

<Item>: Character string

Name of the memo item of the data file into which the binary file must be added.
If only <Data file> and <Item> are specified, HLinkMemo cancels the existing link between the binary file and the item.

<File to attach>: Optional character string

Name of the file that will be associated with the binary memo item. This name can correspond to:
the full path of the file to attach,
a relative path (respective to the current directory) of the file to attach.
If this parameter is not specified or is an empty string (""), the current attachment is deleted..
If a path is specified, this path must correspond to an existing file. Otherwise, a fatal error is displayed.

<Type>: Optional combination of Integer constants

Indicates the type of file to attach and its read mode.
hAcceptOpenedFile Allows you to read the source file that will be added to the memo if this source file is opened in write mode somewhere else.
This constant can be used with the constants for file type.
hMemoBin
(default value) The file is an ordinary binary file.
hMemoImg The file is an image file.
hMemoOle The file is an OLE file.
hMemoWav The file is a sound file.

This parameter is ignored.
This parameter is available for the data files in HFSQL format only.

<Information>: Optional character string

Information message (up to 65535 characters) stored with the file. This message can be read again by HInfoMemo.
This parameter is ignored.
This parameter is available for the data files in HFSQL format only.

Associating a file with a binary memo item via a Record type variable Hide the details

<Result> = HLinkMemo(<Memo item> [, <File to attach> [, <Type> [, <Information>]]])

<Result>: Boolean

True if the operation was performed,
False if a problem occurs. HError is used to identify the error. The function will return an error if the file to associate is opened in write mode and if the hAcceptOpenedFile constant was not used.

<Memo item>: Record variable

Memo item where the binary file must be added. Use the following notation: <Name of record variable>.<Name of memo item>.
If only the <Memo item> parameter is specified, HLinkMemo cancels the existing link between the binary file and the item.

<File to attach>: Optional character string

Name of the file that will be associated with the binary memo item. This name can correspond to:
the full path of the file to attach,
a relative path (respective to the current directory) of the file to attach.
If this parameter is not specified or is an empty string (""), the current attachment is deleted.

<Type>: Optional combination of Integer constants

Indicates the type of file to attach and its read mode.
hAcceptOpenedFile Allows you to read the source file that will be added to the memo if this source file is opened in write mode somewhere else.
This constant can be used with the constants for file type.
hMemoBin
(default value) The file is an ordinary binary file.
hMemoImg The file is an image file.
hMemoOle The file is an OLE file.
hMemoWav The file is a sound file.

<Information>: Optional character string

Information message (up to 65535 characters) stored with the file. This message can be read again by HInfoMemo.
This parameter is ignored.

Remarks

Canceling the existing link

If only <Data file> and <Item> are specified, HLinkMemo cancels the existing link between the binary file and the item.

Difference between BinaryLoad and HLinkMemo

Unlike BinaryLoad (kept for compatibility with WINDEV 5.5), HLinkMemo does not load the binary file in memory. Therefore, there is no risk of memory overload when a large file is associated with a binary memo item.

HFSQL thumbnails

If the item uses HFSQL thumbnails, they will be automatically generated with the new file when the record is added or modified (HAdd, HModify or HWrite).

Managing memos in SQLite

Storing information in memo format is recommended for the data whose size is less than 1 MB. We advise you to directly save the data in external file format on the internal or external memory of the phone and to store the access path to this data in the database.

Component: wd300hf.dll