1004 SETUP-5\n\nSetup cannot access registry. Some of the changed settings will not be saved.
1005 SETUP-6\n\nNo engine is loaded.
1006 SETUP-7\n\nThe specified setting is invalid.
1007 SETUP-10\n\nOnly one instance is allowed to run.
1008 For SETUP changes to take effect, stop and start the engine(s). This step is not necessary if you changed only TRACE settings and already applied the changes to the current Microkernel session.
1009 You have not saved your changes.\nDo you want to save them now?
1010 SETUP-11:\n\n Incomplete Definition: Dictionary location must be specified.
1011 SETUP-12:\n\n Add operation not allowed. The maximum number of Data File Locations (8) have been defined.
1012 SETUP-13:\n\n Incomplete Definition: At least one data file location must be specified.
1013 SETUP-14:\n\n Are you sure you want to delete the following named database reference: %s ?
1014 SETUP-15:\n\n Setup is not able to load the WDBNM32.DLL named database operations cannot be performed.
1015 SETUP-15:\n\n Setup is not able to load the WDBNAMES.DLL named database operations cannot be performed.
1016 Do you want to apply TRACE changes to the current session of the Microkernel?
1017 SETUP-16:\n\n Wrong DLL Version: This is not the current version of WDBUEI32.DLL.
1100 BTI Database Setup Utility
1101 About BTI Database Setup Utility
1102 BTI Communications Server
1103 Microkernel DB Engine
1104 Scalable SQL Engine
1105 5.x
1106 6.x
1107 Cursor Stability
1108 Exclusive
1109 On
1110 Off
1111 BTI Database Setup Utility
1112 Limited by Memory
1113 WSSETUP
1114 NTSSETUP
1115 WMSETUP
1116 NTMSETUP
1117 Modify Database Name
1118 Delete
1119 Workstation
1120 Server
1121 Multi Engine
1122 Single Engine
1123 Yes
1124 No
1200 This category contains settings related to files, file handles, record locks, indexes, and log files.
1201 This category contains settings related to the size of buffers the Microkernel must allocate for various purposes.
1202 This category contains settings related to transactions, including the number supported and how and when they will be logged.
1203 This category contains settings related to the number of clients and threads supported as well as the location of various system files.
1204 This category contains settings related to tracing various Btrieve operations. Tracing is an Advanced feature used mainly for debugging purposes.
1220 The maximum number of unique files that \ncan be open at one time. This value \nrepresents the maximum number of physical file handles that the Microkernel can open.
1221 The maximum number of logical file \nhandles that the Microkernel uses at \none time. Each file can be opened by \nmultiple client instances, resulting \nin different logical handles for the same physical file handle.
1222 The maximum number of records each \nclient instance can lock at one time. \nThis maximum applies to both single and multiple-record read locks.
1223 Specifies that the Microkernel should \nattempt to balance existing index pages \nrather than create a new one whenever an index page in a file becomes full.
1224 Specifies that all new files are created \nin v5.x file format. Turn on this setting \nonly if you need backward compatibility with a previous version of Btrieve.
1225 Controls whether the Microkernel keeps \na log of operations executed on selected \nfiles. If you turn off this setting, the \nMicrokernel performs no logging.
1226 Advanced: If you turn on the Log \nSelected Files setting, this setting \nspecifies whether to use the v6.x or v5.x log file format whenever you create a new log file.
1227 Specifies the size of the cache (in \nkilobytes) that the Microkernel allocates. \nThe Microkernel uses this cache for all \nBtrieve file accesses.
1228 (Formerly Largest Record Size) Specifies \nthe maximum size of the communication \nbuffer (in bytes) that the Microkernel\ncan submit or return. Each worker thread \nallocates a memory buffer large enough \nto accommodate this maximum length of data.
1229 Determines the size of a buffer (in \nkilobytes) used when accessing files \ncreated with the Data Compression file \nattribute. If you do not use compressed \nfiles, set this value to 0.
1230 Advanced: Specifies the size (in \nkilobytes) of the buffer required to \nhandle extended (multiple record) \noperations.
1231 Advanced: Specifies the maximum \namount of memory (in kilobytes) \nthat the Microkernel can allocate for \nsorting purposes during run-time \ncreation of indexes. If the value \nis zero, the Microkernel allocates \nas much memory as needed upto 60% of the available physical memory.
1232 Specifies the maximum number of user \ntransactions that can be active at the same time.
1233 Specifies how transactions are \ncommitted to permanent disk storage. \nYou turn this setting on to instruct the \nMicrokernel that system transactions \ncontaining user transactions must be \ncompleted when a client issues the End \nTransaction operation and before the \nMicrokernel returns the successful status \ncode to the client. Turning off this \nsetting provides enhanced performance.
1234 Advanced: Specifies the maximum \nnumber of operations (performed on any \none file) required to trigger a system \ntransaction. The Microkernel initiates \na system transaction when it reaches \nthe bundle limit or the Initiation Time Limit, whichever comes first.
1235 Advanced: This setting specifies the \ntime limit (in milliseconds) that \ntriggers a system transaction. The \nMicrokernel initiates a system \ntransaction when it reaches the \nOperation Bundle Limit or the time limit, whichever comes first.
1236 Advanced: If the Microkernel is \ncurrently processing a system transaction \n and an application requests another \nsystem transaction, this setting specifies \nhow long (in milliseconds) to wait before \nattempting to initiate the new system transaction.
1237 Advanced: This setting specifies the \nmaximum number of pages written in a group during a system transaction.
1238 Each Btrieve-based application is a \nclient of the Microkernel. This setting \nspecifies the maximum number of clients \nthat can access the Microkernel at one time.
1239 Advanced: Specifies how many worker \nthreads the Microkernel initially spawns \nto handle client requests. Worker \nthreads are the elements that actually \nperform file operations on behalf of \nthe requesting client process. The Microkernel may dynamically spawn additional worker threads as needed.
1240 Advanced: Specifies how many \nbackground I/O threads the Microkernel \nspawns. The I/O threads perform all \nactual disk I/O on a file. Because the \nMicrokernel does not spawn additional \nI/O threads, you should specify the maximum number you anticipate needing.
1241 Advanced: Specifies that the Microkernel \nallocate resources, including threads and \nmemory buffers, when the Microkernel is \nstarted. By default, the Microkernel does \nnot allocate any resources until the first operation request.
1242 Advanced: Causes the Microkernel to \nfree all memory and thread resources \nto the system and return to a minimal state (no resources allocated) when there are no active clients.
1243 Specifies the location the Microkernel \nuses to store some system files and is a \ndefault location for other items, such as the transaction and trace file.
1244 Specifies where the Microkernel can \ncreate temporary work files used for \ninternal operations such as mergesort. \nIf not specified, the Microkernel uses the directory where the data file is located.
1245 Advanced: Specifies whether to enable \nthe trace feature to trace each API call \nto a trace file. Developers can use \ntracing to debug applications. If you turn this option on, you need to specify a trace file.
1246 Advanced: Specifies the file where the Microkernel should write trace information.
1247 Advanced: Specifies a list of Btrieve \nOperations which will be traced. Separate \neach operation number with a comma. For example, to trace the open, close, and get first operations enter 0,1,12
1248 Advanced: Specifies the size of the data \nbuffer that the Microkernel writes to the trace file when you enable the tracing feature.
1249 Advanced: Specifies the size of the key \nbuffer that the Microkernel writes to the trace file when you enable the tracing feature.
1320 Settings for the BTI Communications Server for the Microkernel Database Engine.
1321 Settings for the BTI Communications Server for the Scalable SQL Engine.
1340 Specifies the maximum number of remote tasks that can access the server at any given time.
1341 Advanced: Specifies how many worker \nthreads the BTI Communications Server \nspawns to handle client requests. Worker \nthreads are the elements that actually \nperform file operations on behalf of the requesting client process.
1342 Advanced: Specifies whether to enable \nthe BTI Communications Server to accept \nremote requests. It "advertises" the \npresence of the Engine to remote servers and workstations.
1343 Advanced: Specifies the size of the \nbuffer (in bytes) that the engine reads \nfor packets from the OS communication \nlayer. The value is rounded up to the \nnearest mutiple of the system page size \n(4K on Intel platforms) at the time that the engine allocates the buffer.
1344 Specifies the maximum number of remote tasks that can access the server at any given time.
1345 Advanced: Specifies how many worker \nthreads the BTI Communications Server \nspawns to handle client requests. Worker \nthreads are the elements that actually \nperform file operations on behalf of the requesting client process.
1346 Advanced: Specifies whether to enable \nthe BTI Communications Server to accept \nremote requests. It "advertises" the \npresence of the Engine to remote servers and workstations.
1347 Advanced: Specifies the size of the \nbuffer (in bytes) that the engine reads \nfor packets from the OS communication \nlayer. The value is rounded up to the \nnearest mutiple of the system page size \n(4K on Intel platforms) at the time that the engine allocates the buffer.
1360 This category contains settings related to the Scalable SQL system configuration.
1361 This category contains settings related to manipulating the Scalable SQL trace or log file.
1380 Advanced: Specifies how many worker \nthreads the Scalable SQL initially \nspawns to handle client requests. \nWorker threads are the elements that \nactually perform file operations on \nbehalf of the requesting client process. The Scalable SQL may dynamically spawn additional worker threads as needed.
1381 (Formerly Maximum Message Length) \nSpecifies the maximum size of the \ncommunication buffer (in bytes) that \nthe Scalable SQL can submit or return. \nEach worker thread allocates a memory buffer large enough to accommodate this maximum length of data.
1382 Allows you to specify the maximum number of tables Scalable SQL allows in a single join.
1383 An isolation level is the level of data \nlocking that Scalable SQL employs to \nprovide isolation from other changes. \nThis option allows you to set the \nisolation level Scalable SQL uses if \nan application fails to set one. Cursor \nStability: Scalable SQL implements \nrow-level or page-level locking on the \nfile. Exclusive: Scalable SQL \nimplements file-level locking and the locks will be released when the transaction is complete.
1384 Specifies the directory in which you \nwant Scalable SQL to store the temporary \nfiles it creates during certain processes. This directory must exist before Scalable SQL accesses it.
1385 Advanced: Specifies whether to enable \nthe trace feature to record database login and logout activity to a trace file.
1386 Advanced: Specifies whether to enable \nthe trace feature to record failed database login attempts to a trace file.
1387 Advanced: Specifies whether to enable \nthe trace feature to record all data definition and data manilulation activity to a trace file.
1388 Advanced: Specifies the file where the Scalable SQL should write trace information.
1389 Advanced: Deletes the Scalable SQL trace file.
1400 This category contains settings related to files, file handles, record locks, indexes, and log files.
1401 This category contains settings related to the size of buffers the Microkernel must allocate for various purposes.
1402 This category contains settings related to transactions, including the number supported and how and when they will be logged.
1403 This category contains settings related to the number of clients and threads supported as well as the location of various system files.
1404 This category contains settings related to tracing various Btrieve operations. Tracing is an Advanced feature used mainly for debugging purposes.
1420 The maximum number of unique files that \ncan be open at one time. This value \nrepresents the maximum number of physical file handles that the Microkernel can open.
1421 The maximum number of logical file \nhandles that the Microkernel uses at \none time. Each file can be opened by \nmultiple client instances, resulting \nin different logical handles for the same physical file handle.
1422 The maximum number of records each \nclient instance can lock at one time. \nThis maximum applies to both single and multiple-record read locks.
1423 Specifies that the Microkernel should \nattempt to balance existing index pages \nrather than create a new one whenever an index page in a file becomes full.
1424 Specifies that all new files are created \nin v5.x file format. Turn on this setting \nonly if you need backward compatibility with a previous version of Btrieve.
1425 Controls whether the Microkernel keeps \na log of operations executed on selected \nfiles. If you turn off this setting, the \nMicrokernel performs no logging.
1426 Advanced: If you turn on the Log \nSelected Files setting, this setting \nspecifies whether to use the v6.x or v5.x log file format whenever you create a new log file.
1427 Advanced: Tells whether to delete temporary lock files created during multi-engine file sharing. Deleting may cause Status 81 on peer-to-peer networks.
1428 Controls whether the MKDE opens files on local disks exclusively (Single Engine), or in shared mode (Multi Engine).
1429 This setting controls whether the MKDE opens files on remote disks exclusively (Single Engine), or in shared mode (Multi Engine).
1430 Controls whether applications can open files using a Btrieve operation with a bias that specifies that individual files can be shared.
1431 Advanced: Sets the number of system transactions performed during write operations for shared files.
1432 Specifies the size of the cache (in \nkilobytes) that the Microkernel allocates. \nThe Microkernel uses this cache for all \nBtrieve file accesses.
1433 (Formerly Largest Record Size) Specifies \nthe maximum size of the communication \nbuffer (in bytes) that the Microkernel\ncan submit or return. Each worker thread \nallocates a memory buffer large enough \nto accommodate this maximum length of data.
1434 Determines the size of a buffer (in \nkilobytes) used when accessing files \ncreated with the Data Compression file \nattribute. If you do not use compressed \nfiles, set this value to 0.
1435 Advanced: Specifies the size (in \nkilobytes) of the buffer required to \nhandle extended (multiple record) \noperations.
1436 Advanced: Specifies the maximum \namount of memory (in kilobytes) \nthat the Microkernel can allocate for \nsorting purposes during run-time \ncreation of indexes. If the value \nis zero, the Microkernel allocates \nas much memory as needed upto 60% of the available physical memory.
1437 Specifies the maximum number of user \ntransactions that can be active at the same time.
1438 Specifies how transactions are \ncommitted to permanent disk storage. \nYou turn this setting on to instruct the \nMicrokernel that system transactions \ncontaining user transactions must be \ncompleted when a client issues the End \nTransaction operation and before the \nMicrokernel returns the successful status \ncode to the client. Turning off this \nsetting provides enhanced performance.
1439 Advanced: Specifies the maximum \nnumber of operations (performed on any \none file) required to trigger a system \ntransaction. The Microkernel initiates \na system transaction when it reaches \nthe bundle limit or the Initiation Time Limit, whichever comes first.
1440 Advanced: This setting specifies the \ntime limit (in milliseconds) that \ntriggers a system transaction. The \nMicrokernel initiates a system \ntransaction when it reaches the \nOperation Bundle Limit or the time limit, whichever comes first.
1441 Advanced: If the Microkernel is \ncurrently processing a system transaction \n and an application requests another \nsystem transaction, this setting specifies \nhow long (in milliseconds) to wait before \nattempting to initiate the new system transaction.
1442 Advanced: This setting specifies the \nmaximum number of pages written in a group during a system transaction.
1443 Each Btrieve-based application is a \nclient of the Microkernel. This setting \nspecifies the maximum number of clients \nthat can access the Microkernel at one time.
1444 Advanced: Specifies how many worker \nthreads the Microkernel initially spawns \nto handle client requests. Worker \nthreads are the elements that actually \nperform file operations on behalf of \nthe requesting client process. The Microkernel may dynamically spawn additional worker threads as needed.
1445 Advanced: Specifies how many \nbackground I/O threads the Microkernel \nspawns. The I/O threads perform all \nactual disk I/O on a file. Because the \nMicrokernel does not spawn additional \nI/O threads, you should specify the maximum number you anticipate needing.
1446 Advanced: Specifies that the Microkernel \nallocate resources, including threads and \nmemory buffers, when the Microkernel is \nstarted. By default, the Microkernel does \nnot allocate any resources until the first operation request.
1447 Advanced: Causes the Microkernel to \nfree all memory and thread resources \nto the system and return to a minimal state (no resources allocated) when there are no active clients.
1448 Specifies the location the Microkernel \nuses to store some system files and is a \ndefault location for other items, such as the transaction and trace file.
1449 Specifies where the Microkernel can \ncreate temporary work files used for \ninternal operations such as mergesort. \nIf not specified, the Microkernel uses the directory where the data file is located.
1450 Advanced: Specifies whether to enable \nthe trace feature to trace each API call \nto a trace file. Developers can use \ntracing to debug applications. If you turn this option on, you need to specify a trace file.
1451 Advanced: Specifies the file where the Microkernel should write trace information.
1452 Advanced: Specifies a list of Btrieve \nOperations which will be traced. Separate \neach operation number with a comma. For example, to trace the open, close, and get first operations enter 0,1,12
1453 Advanced: Specifies the size of the data \nbuffer that the Microkernel writes to the trace file when you enable the tracing feature.
1454 Advanced: Specifies the size of the key \nbuffer that the Microkernel writes to the trace file when you enable the tracing feature.
1500 This catagory contains settings related to how applications choose which Microkernel engine to use for Btrieve requests.
1520 (Windows NT only) Tells the MKDE Interface where to pass requests when both a workstation and a server engine are available.
1521 Tells the MKDE Interface whether the local Workstation Engine should be used to access a file.
1522 Specifies whether the Btrieve Requester Interface will allow access to a Microkernel Server Engine running on a remote server.
