UNLOCK: Difference between revisions
Jump to navigation
Jump to search
Navigation:
Main Page with Articles and Tutorials
Keyword Reference - Alphabetical
Keyword Reference - By usage
Report a broken link
m (Protected "UNLOCK" ([Edit=Allow only autoconfirmed users] (indefinite) [Move=Allow only autoconfirmed users] (indefinite))) |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 16: | Line 16: | ||
* [[LOCK]] and [[UNLOCK]] statements are always used in pairs and each statement must match the other one. | * [[LOCK]] and [[UNLOCK]] statements are always used in pairs and each statement must match the other one. | ||
* Files must be unlocked before other programs can access them, and before the file is closed. | * Files must be unlocked before other programs can access them, and before the file is closed. | ||
* [[ | * '''[[Keywords currently not supported by QB64#Keywords_not_supported_in_Linux_or_macOS_versions|Keyword not supported in Linux or macOS versions]]''' | ||
Latest revision as of 02:30, 24 January 2023
This statement opens access to parts or all of a file to other programs and network users.
Syntax
- UNLOCK [#]fileNumber%
- UNLOCK [#]fileNumber%, record&
- UNLOCK [#]fileNumber%, [firstRecord&] TO lastRecord&
Description
- fileNumber% is the file number of the file to unlock.
- In the first syntax, the entire file is unlocked.
- In the second syntax, record& is the record number of the file to unlock.
- In the third syntax, the records or bytes in the range [firstRecord&,lastRecord&] are unlocked. If firstRecord& is omitted, it is assumed to be the first record or byte.
- For files opened in BINARY mode, each record corresponds to a single byte.
- LOCK and UNLOCK statements are always used in pairs and each statement must match the other one.
- Files must be unlocked before other programs can access them, and before the file is closed.
- Keyword not supported in Linux or macOS versions
See also