<Source>.LinkMemo (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Canceling the existing link

Difference between BinaryLoad and <Source>.LinkMemo

<Source>.LinkMemo and Remote Access (RPC)

HFSQL thumbnails

Managing memos in SQLite

See also

<Source>.LinkMemo (Function)

In french: <Source>.AttacheMé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 (<Source>.Add, <Source>.Modify or <Source>.Write). The function will return an error if the file is opened in write mode and if the hAcceptOpenedFile constant was not used.

<Source>.ExtractMemo will be used to extract the file contained in the memo onto the hard disk.

Remark: You also have the ability to use the direct assignment:

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:

bufFichier is TO Buffer = fLoadBuffer("MyFile")
MyFile.MyMemo = bufFile

Versions 15 and later

This function is now available for Android applications.

New in version 15

This function is now available for Android applications.

Versions 17 and later

This function is now available for iPhone/iPad applications.

New in version 17

This function is now available for iPhone/iPad applications.

Versions 18 and later

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

New in version 18

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

This function is now available in Android Widget mode.

This function is now available in Windows Store apps mode.

Versions 21 and later

This function is now available in Universal Windows 10 App mode.

New in version 21

This function is now available in Universal Windows 10 App mode.

Remark: From version 19, HFSQL is the new name of HyperFileSQL.

Example

// Attach an image to the record
Product.LinkMemo(Product_Img, "C:\Images\Product1.gif", hMemoImg)
// Transfer the content of controls into the file buffer
Product.ToFile()
// Add the record
Product.Add()

Syntax

Associating a file with a binary memo item Hide the details

<Result> = <Source>.LinkMemo(<Item> [, <File to attach> [, <Type> [, <Information>]]])

<Result>: Boolean

True if the operation was performed,
False if a problem occurred. 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.

<Source>: Type corresponding to the specified source

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

<Item>: Character string (with or without quotes)

Name of the memo item of the data file into which the binary file must be added.
If only <Source> and <Item> are specified, <Source>.LinkMemo 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.
No relative path can be used.
If this parameter is not specified or if it corresponds to an empty string (""), the current link 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 <Source>.InfoMemo.
This parameter is ignored.
This parameter is available for the data files in HFSQL format only.

Remarks

Canceling the existing link

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

Difference between BinaryLoad and <Source>.LinkMemo

Unlike BinaryLoad, <Source>.LinkMemo 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.

<Source>.LinkMemo and Remote Access (RPC)

<Source>.LinkMemo searches for the file to attach to the RPC server.

To insert into a memo a file found locally and not on the RPC server, the memo item must be assigned with its full content, without calling <Source>.LinkMemo.

Example: Insert from a WINDEV Mobile application an image found in the executable directory:

sImage is string
sImage = fExeDir() + "\signature.jpg"
FileBuffer is Buffer
FileBuffer = fLoadText(sImage)
FileOnRPCServer.ImageItem = UnicodeToAnsi(FileBuffer)
FileOnRPCServer.Add()

The image is sent to the RPC server when added. The RPC server includes it into the memo, whether the connection to the database is established via OLE DB or via native access.

HFSQL thumbnails

If the item is using HFSQL thumbnails, the thumbnails will be automatically generated with the new file when adding or modifying the record (<Source>.Add, <Source>.Modify or <Source>.Write).

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: wd260hf.dll