5024 - Query string empty! Unable to identify record!

This error is generated user tries to update (edit) record without specifying the vale for every database field defined in WB_UID variable.
Executing update command is possible only if all fields defined in WB_UID have value in WBF_Fields.
E.g.
If
wb_uid=Fname,Lname
then WBF_Fname and WBF_Lname must not be empty.
read more

5023 - No data received! Nothing to add to database!

This error is generated when user tries to add an empty record (by sending an Add command with empty value in all WBF_fields). At least one database field (WBF_fields) must have value set.
read more

5022 - New password check failed!

This error is generated when user submits different values for WB_DBNewPass and WB_DBNPassCh when executing Change Password command (WB_Command=CP).

read more

5021 - Invalid value for True/False field!

This error is generated when database field of type Boolean (True/False) gets invalid value in WBF_field. Valid settings are:
for True value:
-1
1
T
TRUE
ON
Y
YES
for False value:
0 (zero)
NO
N
OFF
F
FALSE
Any other value will generate this error message!

read more

5020 - Invalid data passed to UrlEncode() function.

Reserved for future use. If you get this error message, please send us description of operation that caused this error!
read more

5019 - Invalid data passed to UrlDecode() function.

This error is generated when a browser parse form data containing the percentage (%) character to WBSP engine. E.g. if the browser mistakenly called WBSP file with the following
http://www.domain.com/somefile.wbsp?WB_BaseName=base.mdb&WB_Query=100% free&...
If you use form for sending data to WBSP file your browser and WBSP engine will take care of transferring the data.
read more

5018 - Invalid command string!

This error is generated when WBSP engine does not recognize WB_Command value.
read more

5017 - Incorrect password!

This error is generated when user submits invalid value for WB_DBOldPass when executing Change Password command (WB_Command=CP).
read more

5016 - Illegal use of unregistered trial version of WhizBase engine!

This error does not exist since WhizBase v. 4.000
read more

5015 - Illegal unique identifier! Query returned no records!

This error is generated when user tries to update or delete a record and query created upon WB_UID field returns no records. The record does not exist, try typing other value for WBF_Fields that identify the record.
read more

5014 - Illegal unique identifier! Query returned more than one record!

This error is generated when user tries to update or delete a record and query created upon WB_UID field returns more than one record. The solution is to check again the WB_UID value and to create new combination of database fields for WB_UID that will uniquely identify every record.
read more

5013 - Illegal referring page!

This error is generated when someone try to execute WhizBase command that require referrer check either from server that is not included in referrer list (Referrer check section), or by typing the URL in "Address" field of browser or using window.open() JavaScript function!
If you want to enable executing command only from authorized web servers (domains) include server name in referrer line in file Referrer check section.
read more

5012 - Error reading system file !

This error does not exist since WhizBase v. 4.000
read more

5011 - Empty mailing list recordset!

This error is generated when user tries to execute Mail List command (WB_Command=L) and resulting recordset is empty.
read more

5010 - Duplicate value in UID!

This error is generated when user tries to add a record with defined WB_UID variable, and record with same value in fields defined in WB_UID already exists. Change the value in field(s) included in WB_UID.
read more

5 - Invalid procedure call or argument

This error can be generated for various reasons but most usual case is when WBSP engine receives invalid registration key value.
It can also be caused by invalid argument of $WBFN function.
read more

429 - ActiveX component can't create object.

This error is generated when DAO, ADO, Scripting server or HTMLMailer are not installed properly on the web server. If this error is generated by DAO or ADO try changing the WB_DBObject variable. If all values reports the same error then it is required to install Jet engineering on the web server.
If error was generated by HTMLMailer then it is required to install WhizBase on the web server.
read more

3633 - Driver: MS Access; produced following error: Can't load DLL: 'MSJET35.DLL'

This error is generated when web server does not have MS Jet 3.5 database support. To solve this please install all necessary files on the web server. For more info please contact us at support@whizbase.com.
read more

3265 - Item not found in this collection.

This error is generated when WhizBase tries to access database table or field that does not exist.
Possible causes:
Table:
- table does not exist - the WB_RcdSet contains mistyped table name. To solve this check the name(s) of the table(s) defined in WB_RcdSet.
- table name contains dash, underscore, space or other special character. To solve this enclose table name in square brackets.
Field:
- field does not exist in the recordset. Make sure you spelled the field name correctly.
- there is more than one field with this name in the recordset (e.g. using complex recordset generated from two tables having few fields with same name); to solve this problem use $WBF[tablename.fieldname] and WBF_tablename.fieldname instead of $WBF[fieldname] and WBF_fieldname.
read more

3170 - Couldn't find installable ISAM.

This error is generated when WBSP engine is unable to locate required ISAM libraries.
If WBSP engine is installed properly (no errors reported during the test mode) then the error is probably caused by mistyped WB_Connect value (check the semicolon at the end of WB_Connect value).
read more

3146 - ODBC--call failed.

This error may occur when the ODBC data source is on a network drive and user is not connected to the network or network is unavailable to user for any other reason. Make sure the network is available, and then try the operation again.
If this does not help make sure that user has the necessary permissions to access the ODBC source and the network drive. Remember that WBSP scripts are executed by user "internet_user", "nobody", "guest", etc.
read more

3061 - Too few parameters. Expected 'number'

In some cases, this message is generated when unknown field names or expressions are interpreted as query parameters. Be sure to enclose field names containing spaces or punctuation with square brackets [ ].
read more

3051 - The Microsoft Jet database engine cannot open the file 'file name'. It is already opened exclusively by another user, or you need permission to view its data.

This error is generated when WBSP engine tries to open MS Access database and Jet engine is not able to complete operation.
Possible causes:
- Your permissions in system.md? file are not valid for required operation. You must have permission to read data in the specified file in order to view its data. To change your permission assignments, see your system administrator or the table or query's creator.
- WhizBase does not have write access on the directory where database is located and was unable to create file name.LDB file. Assign WBSP engine write permissions over the directory where the database file is located.
read more

3027 - Driver: Text; produced following error: Can't update. Database or object is read-only.

Text ISAM (driver) does not support deleting and updating records.
However, it supports adding and reading records so it can be used for all WhizBase operations that do not require deleting or updating records.
If these features are required use other database type.
read more

13 - Type mismatch

WhizBase is not very sensible to variable's data type. However, working with database fields require proper data type for every field type. This error occures when Numeric, Boolean and TimeDate field receives value that can not be converted (e.g. string instead of number or date in invalid format, etc.).
read more