Copyright: Built on   Tue Jun 25 22:56:49 1996


Syntax error in number. (Error 2420)

You entered a value that is invalid. This can occur if a nonnumeric value is provided as part of the expression.


Syntax error in date. (Error 2421)

Date syntax is incorrect. This error occurs if you specify an invalid date. For example, 9/31/94 is invalid (September has only 30 days).


Syntax error in string. (Error 2422)

You entered an expression that includes an invalid string. Check the expression to make sure you entered it correctly.


Invalid use of '.', '!', or '()'. (Error 2423)

The expression doesn't use delimiters correctly. To reference the properties of a DAO object, it is recommended that you use the .propertyname syntax.


Unknown name. (Error 2424)

You entered an expression that has a field or property name that can't be recognized. Make sure the object exists, or check the expression to make sure you entered it correctly.


Unknown function name. (Error 2425)

You entered an expression with a function name that can't be recognized. Make sure the function exists, or check the expression to make sure you entered it correctly.


Function isn't available in expressions. (Error 2426)

You have entered a function that can't be used in this expression. The functions DoEvents, LBound, UBound, Spc, and Tab aren't available in expressions.


Object has no value. (Error 2427)

You entered an expression containing an identifier for an object that has no value. (Objects may have a default property value or return a default method.)

Check the expression to make sure you entered it correctly.


Invalid arguments used with domain function. (Error 2428)

You have entered an invalid argument in an aggregate function. For information on the function's arguments, see SQL Aggregate Functions, and then choose the name of the function.


In operator without (). (Error 2429)

When coding an SQL statement that includes the In operator, you must surround the list of items to test with parentheses. For example, to see if a value is one of a set of values, you could use the following code in the WHERE clause of an SQL query:

WHERE Region In ('TX', 'CA', 'WA')

This code tests to see if the Region field contains any of the above abbreviations, which represent Texas, California, and Washington.


Between operator without And. (Error 2430)

When using the Between operator to test whether a value of an expression lies within a specified range of values, specify the upper and lower limits of the range separated with the reserved word And. For example, to test for a range of A to C, you could use the following code:

WHERE fldName Between "A" And "C"


Syntax error (missing operator). (Error 2431)

The expression or statement is missing an operator.


Syntax error (comma). (Error 2432)

The expression or statement uses a comma where it doesn't belong or is missing a comma to separate arguments.


Syntax error. (Error 2433)

The wording or punctuation of the command isn't correct. It may be missing an operator, or you may have specified an operator that does not exist.


Syntax error (missing operator). (Error 2434)

The expression or statement is missing an operator.


Extra ). (Error 2435)

You entered an expression that has too many closing parentheses. Delete any parenthesis that doesn't have a matching opening parenthesis.


Missing ), ], or Item. (Error 2436)

You entered an expression that is missing a closing parenthesis, bracket, or vertical bar. Check the expression to make sure you entered it correctly.


Invalid use of vertical bars. (Error 2437)

You entered an expression that has invalid vertical bars (|). Check the expression to make sure you entered it correctly.


Syntax error. (Error 2438)

You entered an expression that has invalid syntax. For example, an operand or operator may be missing, you may have entered an invalid character or comma, or you may have entered text without surrounding it by quotation marks ("). Check the expression to make sure you entered it correctly.


Wrong number of arguments used with function. (Error 2439)

You entered an expression that has a function with the wrong number of arguments. Check the function to verify how many arguments it takes, or check the expression to make sure you entered it correctly.


IIF function without (). (Error 2440)

The IIf function requires parentheses around its arguments, as shown in the following syntax:

IIf(expr, truepart, falsepart)


Invalid use of parentheses. (Error 2442)

You entered an expression that has invalid parentheses. For example, you may be trying to use the parentheses syntax for an identifier in a query. In a query, you can use only the standard identifier syntax.


Invalid use of Is operator. (Error 2443)

The Is operator is used to determine if an expression is Null. You can use the Is operator in an expression only with NULL or NOT NULL.


Expression too complex. (Error 2445)

This expression is too complex for the Microsoft Jet database engine. Try to simplify the expression.


Out of memory during calculation. (Error 2446)

The application doesn't have enough memory to complete the calculation. Make sure you have enough RAM and an established swap file. You may need to terminate other programs, remove desktop wallpaper bitmaps, or remove unneeded device drivers to recover enough memory.


Invalid use of '.', '!', or '()'. (Error 2447)

The expression doesn't use delimiters correctly. To reference the properties of DAO objects, it is recommended that you use the .propertyname syntax.


Can't set value. (Error 2448)

You are trying to assign a value to an object that is read-only or doesn't have a value.


Unrecognized database format <filename>. (Error 3343)

Possible causes:

•	The specified file name is not a Microsoft Jet database.

•	The specified file name is a device name, such as a printer, a console, and so forth.

•	The .mdb file has invalid header information or an unknown sort order.

•	A commit is pending from another user, but the lock file cannot be found.

•	During a commit, you are attempting to write a Long value larger than the 2K maximum page size.

•	The database is damaged. Repair and compact the database, and then try opening it again.


Exceptions table could not be created on import/export. (Error 3618)


Records could not be added to exceptions table. (Error 3619)


The connection for viewing your linked Microsoft Excel worksheet was lost. (Error 3620)

The connection for viewing your linked Microsoft Excel worksheet was lost. The session of Microsoft Excel may have been terminated.


Can't change password on a shared open database. (Error 3621)
Can’t change password on a shared open database. (Error 3621)


You must use the dbSeeChanges option with OpenRecordset when accessing a SQL Server table that has an IDENTITY column. (Error 3622)


Cannot access the FoxPro 3.0 bound DBF file <filename>. (Error 3623)

You tried to access FoxPro Version 3.0 bound .dbf file. Bound files are accessible only through the FoxPro database container they are bound to.


Couldn't read the record; currently locked by another user. (Error 3624)
Couldn’t read the record; currently locked by another user. (Error 3624)

You tried to read a record on a 2K database page that is currently locked by another user. Wait for the other user to finish working with the record, and then try the operation again.


The text file specification <name> does not exist. You can't import, export, or link using the specification. (Error 3625)
The text file specification <name> does not exist. You can’t import, export, or link using the specification. (Error 3625)


The operation failed. There are too many indexes on table <name>. Delete some of the indexes on the table and try the operation again. (Error 3626)

A table in a Microsoft Jet database can have no more than 32 indexes. You cannot create additional indexes on a table with this many indexes. Further, you cannot compact a database containing a table with this many indexes because compacting a database involves creating several new indexes.

Delete one or more indexes from the named table and try the operation again.


Reserved error <Item>; there is no message for this error. (Error 3000)

An unexpected error occurred. The specified code identifies the conditions under which this error can occur. Please contact Microsoft Product Support Services for more information.


Invalid argument. (Error 3001)

You tried to perform an operation that involves a routine in a DLL, and one of the arguments to the routine is invalid. Check your entry to make sure you have specified the correct arguments, and then try the operation again.

This error also occurs when you attempt to use mutually exclusive constants in an argument to a method, such as specifying both dbConsistent and dbInconsistent in the options argument to the OpenRecordset method.


Couldn't start session. (Error 3002)

You tried to initiate an operation that requires a new session, but you've reached the limit of sessions that can be active at one time. Wait for other operations to finish or stop other operations, and then try the operation again.


Couldn't start transaction; too many transactions already nested. (Error 3003)

You tried to nest a transaction more than five levels deep. Use the CommitTrans or Rollback method to save or roll back the current transaction before you begin another one.


<Database name> isn't a valid database name. (Error 3005)

The specified database name doesn't follow the standard naming conventions for file names. The name may be too long for the buffer that contains the path and file name. Enter a new name, and then try the operation again.


Database <name> is exclusively locked. (Error 3006)

You tried to use a database that is currently open for exclusive access by another user. Wait for the other user to finish working with the database, and then try the operation again.


Can't open library database <name>. (Error 3007)
Can’t open library database <name>. (Error 3007)

The specified database is an internal Microsoft Jet database engine library database, which you can't open.


The table <name> is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically. (Error 3008)

You tried to use a table that is currently open for exclusive access by another user, or you tried to programmatically manipulate a table that is open through the user interface. Address the appropriate condition, and then try the operation again.


You tried to lock table <table> while opening it, but the table can't be locked because it is currently in use. Wait a moment, and then try the operation again. (Error 3009)


Table <name> already exists. (Error 3010)

You tried to create or rename a table with a name that already exists in this database. Choose another name, and then try the operation again.

In a multiuser database, this error can also occur if you delete a table, another user creates a table with the same name, and then you try to roll back the deletion of your table. To restore your table, the other user must first delete or rename the new table before you try the rollback operation again.


The Microsoft Jet database engine could not find the object <name>. Make sure the object exists and that you spell its name and the path name correctly. (Error 3011)

Possible causes:

•	The specified object doesn't exist.

•	You misspelled the object name. Check for missing underscores ( _ ) or other punctuation, and make sure you didn't enter leading spaces.

•	If you're trying to open a Btrieve table, the paths indicated in the data definition file File.ddf may be incorrect. Be sure your data (.dat) files are in the correct directories.


Object <name> already exists. (Error 3012)

You tried to create an object with a name that already exists in this database. Choose a different name, and then try the operation again.


Couldn't rename installable ISAM file. (Error 3013)

You tried to rename a Btrieve, dBASE, or Paradox table, but the file that contains that table couldn't be renamed.

Possible causes:

•	The file has been defined as read-only in the operating system or by your network.

•	In a network environment, you don't have write privileges for the file.


Can't open any more tables. (Error 3014)

You've reached the limit on the number of tables that can be opened at one time. Close one or more tables, and then try the operation again.


<Index name> isn't an index in this table. Look in the Indexes collection of the TableDef object to determine the valid index names. (Error 3015)

You tried to use a value that isn't an index. You can determine the valid index names by looking in the Indexes collection of the TableDef object.


Field won't fit in record. (Error 3016)

You tried to import or paste a field that is too large. Consider breaking the field into smaller pieces and then importing or pasting the data to multiple fields or changing the data type of the field.

Records are limited to just under 2K in size, excluding Memo and OLE Object fields.


The size of a field is too long. (Error 3017)

Possible causes:

•	You tried to define or create a Text field longer than 254 characters. Use a number between 1 and 254, and then try the operation again, or create a Memo field for the data..

•	You tried to define a query parameter longer than 255 characters.


Couldn't find field <name>. (Error 3018)

Possible causes:

•	The specified field doesn't exist.

•	You misspelled the field name. Check for missing underscores ( _ ) or other punctuation, and make sure you didn't enter leading spaces.

•	You entered an invalid field identifier. For example, [My Table]_[My Field] instead of MyTable![My Field].

•	You did not use brackets to surround a field name that contains spaces.


Operation invalid without a current index. (Error 3019)

Set the Index, and then try the operation again.


You tried to call Update or CancelUpdate or attempted to update a Field in a recordset without first calling AddNew or Edit. (Error 3020)

On a Microsoft Jet database, you called the Update or CancelUpdate method but didn't use the AddNew or Edit method before writing data to a record.

On an ODBCDirect database, this error occurs when you attempt to write data to a record without first calling AddNew or Edit.


No current record. (Error 3021)

This error occurs after the unsuccessful application of one of the Find methods or the Seek method, when the underlying Recordset contains no records or the record has been deleted. Move to or select another record, and try the operation again. If the Recordset is empty, you cannot position to a current record. Check the BOF and EOF properties.


The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again. (Error 3022)

You tried to duplicate a value in a field that is the underlying table's primary key or an index that doesn't allow duplicates. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries, and try again.


AddNew or Edit already used. (Error 3023)

You haven't saved or rolled back the current changes and are trying to add or change another record. Use the Rollback or Update method, and then use the AddNew or Edit method.


Couldn't find file <name>. (Error 3024)

Possible causes:

•	The specified file doesn't exist.

•	You misspelled the file name. Check for missing underscores ( _ ) or other punctuation, and make sure you didn't enter leading spaces.

•	The network connection has failed or has not been established.


Can't open any more files. (Error 3025)

You've reached the limit on the number of files that can be opened at one time. Close one or more files, and then try the operation again.


Not enough space on disk. (Error 3026)

You tried to perform an operation that requires more disk space than is available. Remove unused files from your disk, compress your database, and then try the operation again.


Can't update. Database or object is read-only. (Error 3027)

You tried to save changes in a database that was opened for read-only access.

The database is read-only for one of these reasons:

•	You used the OpenDatabase method and opened the database for read-only access.

•	In Visual Basic, you are using the Data control, and you set the ReadOnly property to True.

•	The database file is defined as read-only in the operating system or by your network.

•	The database file is stored on read-only media.

•	In a network environment, you don't have write privileges for the database file.

•	When working with a secured database, the database or one of its objects (such as a field or table) may be set to read-only. You may not have permission to access this data with your user name and password.

Close the database, resolve the read-only condition, and then reopen the file for read/write access.


Can't start your application. The workgroup information file is missing or opened exclusively by another user. (Error 3028)

To ensure referential integrity in databases created by the Microsoft Jet database engine, your application must read the Microsoft Jet database's System.mdw file. Make sure the file is in the location specified in the SystemDB value of the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\Jet\3.5\Engines\Jet key in the Windows Registry.


Not a valid account name or password. (Error 3029)

You entered an invalid account (user) name or password.

User names

User names can be from 1 to 20 characters long and can include alphabetic characters, accented characters, numbers, spaces, and symbols, with the following exceptions:

•	The characters "  /  \  [  ]  |  <  >  +  =  ;  ,  :  ?  *

•	Leading spaces

•	Control characters

User names are not case-sensitive.

Passwords

Passwords can be any combination of 14 or fewer characters; passwords can't contain control characters. Passwords are case-sensitive.


<Account name> isn't a valid account name. (Error 3030)

The specified account (user) name isn't valid. User names can be from 1 to 20 characters long and can include alphabetic characters, accented characters, numbers, spaces, and symbols, with the following exceptions:

•	The characters "  /  \  [  ]  |  <  >  +  =  ;  ,  :  ?  *

•	Leading spaces

•	Control characters

User names are not case-sensitive.


Not a valid password. (Error 3031)

You've typed an invalid password. Passwords can be any combination of 14 or fewer characters, except control characters. Passwords are case-sensitive.


Can't perform this operation. (Error 3032)

Possible causes:

•	You tried to delete the only user account in the group Admins. The group Admins must have at least one user account. If you want to delete this account, create a new account and add it to the group Admins, or add an existing account to the group Admins, and then delete the account.

•	You tried to put a user in a group to which the user already belongs, by appending either a Group object to a User object's Groups collection that already has a Group object of the same name or a User object to a Group object's Users collection that already has a User object of the same name.


You don't have the necessary permissions to use the <name> object. Have your system administrator or the person who created this object establish the appropriate permissions for you. (Error 3033)

You don't have the necessary permissions for the specified object. To change your permission assignments, see your system administrator or the object's creator.


You tried to commit or roll back a transaction without first using BeginTrans. (Error 3034)

You tried to commit or roll back a transaction that wasn't started with a BeginTrans statement.


Database has reached maximum size. (Error 3036)

To add data to this database, you must first reduce its size by deleting data.


Can't open any more tables or queries. (Error 3037)

You've reached the limit on the number of tables and queries that can be opened at one time. Close one or more tables or queries, and then try the operation again.


Couldn't create index; too many indexes already defined. (Error 3039)

You can't create another index for this table. Consider deleting an existing index to make room for the new index.


Disk I/O error during read. (Error 3040)

The disk could not be read due to an internal disk or drive failure.

Possible causes:

•	You tried to read from a network drive, and the network is temporarily busy, or you're no longer connected to the network. Check the network connection, and then try the operation again.

•	The disk or drive has failed.


Can't open a database created with a previous version of your application. (Error 3041)

You tried to access a database that is in an outdated format. Compact the database and then try the operation again.


Out of MS-DOS file handles. (Error 3042)

Either close some files, close other applications, or increase the number of available MS-DOS file handles.

To increase the number of file handles

1	Edit your CONFIG.sys file using Microsoft Windows Notepad or another text editor. The CONFIG.sys file is usually located in the root directory of your boot drive. If you don't have a CONFIG.sys file on your system, you must create one that contains the line listed in step 2.

2	Look for the line that reads FILES = x, where x is some number. Increase the number specified by the FILES command; the exact number of handles you enter depends on the applications you run and the number of files that are open at any given time. If other applications open multiple files, you may need to specify more file handles.

As you increase the number of file handles, remember that each handle consumes more memory. For additional information, refer to your operating system manual.

3	Exit Microsoft Windows.

4	Reboot your system, and then try the operation again.


Disk or network error. (Error 3043)

An internal disk or drive failure prevents reading from or writing to the disk.

Possible causes:

•	You tried to use a network drive, and the network is temporarily busy, or you're no longer connected to the network. Check the network connection, and then try the operation again.

•	The disk or drive has failed.


<Path> isn't a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides. (Error 3044)

Possible causes:

•	You entered an invalid file specification that contains an invalid path. For example, you might have entered a path that doesn't exist or misspelled an element in the path specification.

•	The specified file is on a network drive and you aren't connected to that drive. Make sure the network is available, and then try the operation again.


Couldn't use <name>; file already in use. (Error 3045)

The specified file is currently being used by another user or session. Wait for the other user or session to finish working with the file, and then try the operation again.


Couldn't save; currently locked by another user. (Error 3046)

You tried to save information on a database page that is currently locked by another user. To save your changes, wait for the other user to finish, and then try the operation again.


Record is too large. (Error 3047)

You defined or imported a table with records larger than 2K. This error occurs when you enter data into the record — not when you define the table structure. Redefine the table by making some fields shorter, removing unneeded fields, or moving some fields to other tables.


Can't open any more databases. (Error 3048)

You've reached the limit on the number of databases that can be opened at one time. Close one or more databases and try the operation again.


Can't open database <name>. It may not be a database that your application recognizes, or the file may be corrupt. (Error 3049)

Possible causes:

•	You tried to open a non-Microsoft Jet database, such as a Btrieve, dBASE, or Paradox database or table. Instead, link the database or table to an existing Microsoft Jet database.

•	You tried to import or link a Paradox database or table, and the associated .px file couldn't be found. Make sure the .px file is in the same directory as the Paradox database or table, and then try the operation again.

•	If the specified database is a Microsoft Jet database, it is corrupted. You should attempt to repair the database. If the database can't be repaired, restore the database from a backup copy, or create a new database.


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

Possible causes:

•	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.

•	You tried to open the indicated file exclusively, but another user already has the file open.


MS-DOS file sharing lock count exceeded. You need to increase the number of locks installed with Share.exe. (Error 3052)

To load Share.exe

1	Exit Microsoft Windows.

2	Using a text editor, add the following line to your autoexec.bat file:

SHARE.EXE /L:500

If you don't have an autoexec.bat file on your system, enter the preceding line at the command prompt before you start Microsoft Windows. The exact number of locks you use depends on the applications you run and the number of files that are locked at any given time. If other applications require file locks, you may need to specify more than 500 locks.

3	If you added Share.exe to your autoexec.bat file, reboot your system.

4	Restart Microsoft Windows, and try the operation again.


Too many client tasks. (Error 3053)

You have too many copies of Visual Basic or Visual Basic applications running at the same time. Close one or more instances.


Too many Memo or OLE Object fields. (Error 3054)

You tried to perform a Btrieve operation that involves too many Memo or OLE Object fields. Reduce the number of Memo and OLE Object fields, and then try the operation again.


Not a valid file name. (Error 3055)

You tried to use a file name that doesn't follow the naming conventions for your operating system. Specify the file name again, and then retry the operation.


Couldn't repair this database. (Error 3056)

This database is corrupted or it isn't a Microsoft Jet database. Restore the corrupted Microsoft Jet database from a backup copy or create a new database.


Operation not supported on linked tables. (Error 3057)

Import data from the table, and then try the operation again.


Index or primary key can't contain a Null value. (Error 3058)

Possible causes:

•	You tried to add a Null value to a primary key field.

•	You tried to add a new record but didn't enter a value in the field that contains the primary key.

•	You executed a query that tried to put a Null value in a primary key field.


Operation canceled by user. (Error 3059)

You stopped the operation before its normal completion. Some data changes may not have been saved.


Wrong data type for parameter <parameter>. (Error 3060)

You tried to use an argument with a data type that conflicts with the data type defined for this parameter. For example, you might have tried to use a string expression that expects a numeric argument with a parameter. Use an argument that has the correct data type, and then try the operation again.


Too few parameters. Expected <number>. (Error 3061)

This parameter query requires the specified number of parameters, which you didn't supply. Provide the expected number of parameters, and run the query again.

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 [ ].


Duplicate output alias <name>. (Error 3062)

You tried to execute an SQL statement that has more than one alias with the same name. The following statement, for example, would produce this error:

SELECT LastName AS Name, FirstName AS Name FROM Employees;

Rename one or more of the aliases, and then try the operation again.


Duplicate output destination <name>. (Error 3063)

You tried to execute a query that contains more than one destination field with the same name.

Possible cause:

•	You created an SQL statement that includes an INSERT INTO, SELECT...INTO, or UPDATE statement that lists the specified field name more than once.

Remove the duplicate fields or alias the destination field names, and try the operation again.


Can't open action query <name>. (Error 3064)

You tried to open an action query using the OpenQueryDef method, which is an obsolete method originally valid only with select queries. The preferred method for executing an action query is to use the Execute method of the QueryDef object.


Can't execute a select query. (Error 3065)

You tried to use the Execute method with a select query. The Execute method is valid only with action queries. Select queries contain a SELECT statement and can return records; action queries do not.


Query must have at least one destination field. (Error 3066)

This error occurs if you don't specify any destination field names when you create a query. Select at least one destination field.


Query input must contain at least one table or query. (Error 3067)

In Microsoft Jet databases, this error occurs if you don't select a table name when you create a query. Select at least one table or query.

In ODBCDirect databases, this error occurs if you attempt to execute a query that does not contain an SQL statement. Include at least one query or stored procedure call in the QueryDef object’s SQL property.


Not a valid alias name. (Error 3068)

The alias you entered doesn't follow standard naming conventions. Enter a new name, and then try the operation again.


The action query <name> cannot be used as a row source. (Error 3069)

You can't use the name of an action query here. Instead, use the name of a select query. To run an action query, use the Execute method instead of the name of an action query as input to the FROM clause.


The Microsoft Jet database engine does not recognize <name> as a valid field name or expression. (Error 3070)

The specified name isn't a recognized field name or a valid expression. In a query, this error can occur if you enter a name that improperly refers to a database, table, or field.

Possible causes with Microsoft Access:

•	You have a parameter in a crosstab query or in a query that a crosstab query or chart is based on, and the parameter data type isn't explicitly specified in the Query Parameters dialog box. To solve the problem:

•	In the query that contains the parameter, specify the parameter and its data type in the Query Parameters dialog box. And;

•	Set the ColumnHeadings property for the query that contains the parameter.

•	In any type of query, you've improperly referred to a database, table, or field. For example, this error can occur if you refer to a field named Salary in an expression, but you misspell the field name, such as [Sallary]*1.1.


This expression is typed incorrectly, or it is too complex to be evaluated. For example, a numeric expression may contain too many complicated elements. Try simplifying the expression by assigning parts of the expression to variables. (Error 3071)

Possible causes:

•	You typed an expression that has invalid syntax. For example, an operand or operator may be missing, you may have typed an invalid character or comma, or you may have typed text without enclosing it with quotation marks ( " ). Check the expression to make sure you typed it correctly.

•	You typed an expression that is too complex. For example, a numeric expression may contain too many complicated elements. Try simplifying the expression by assigning some parts to variables.


Operation must use an updatable query. (Error 3073)

You tried to run, open, or modify a query that isn't updatable.

Possible causes:

•	You attempted to run a query that tried to update a field that can't be updated. For example, you may have created the query in such a way that you tried to update a field on the one side of a one-to-many relationship.

•	You tried to use the obsolete OpenQueryDef method on a query that is in a database opened for read-only access.

The database is read-only for one of the following reasons:

•	You used the OpenDatabase method or the Visual Basic Data control, and opened the database for read-only access.

•	The database file has been defined as read-only in your network operating system.

•	In a network environment, you don't have write privileges for the database file.

Close the database, resolve the read-only condition, and then reopen it for read/write access.

•	You don't have permission to make changes to the query. To change your permission assignments, see your system administrator or the query's creator.


Can't repeat table name <name> in FROM clause. (Error 3074)

You can't list the table name more than once. Remove the extra occurrences of the table name or use an alias. If you are trying to join a table to itself, use an alias to change the second reference to the table.


<Message> in query expression <expression>. (Error 3075)

The expression you typed isn't valid for the reason indicated in the message. Make sure you have typed field names and punctuation correctly, and then try the operation again.


<Name> in criteria expression. (Error 3076)

The expression you entered isn't valid for the reason indicated in the message. Make sure you entered field names and punctuation correctly, and then try the operation again.


<Message> in expression. (Error 3077)

The expression you entered isn't valid for the reason indicated in the message. Make sure you entered field names and punctuation correctly, and then try the operation again.


The Microsoft Jet database engine cannot find the input table or query <name>. Make sure it exists and that its name is spelled correctly. (Error 3078)

Possible causes:

•	The specified table or query doesn't exist.

•	You misspelled the table or query name. Check for missing underscores ( _ ) or other punctuation, and make sure you didn't enter leading spaces.


The specified field <field> could refer to more than one table listed in the FROM clause of your SQL statement. (Error 3079)

The specified field reference could refer to more than one table listed in the FROM clause of your SQL statement. In the following example, the OrderID field exists in both the Orders and Order Details tables:

SELECT OrderID

FROM Orders, [Order Details];

Because the statement doesn't specify which table OrderID belongs to, it produces this error. To complete this operation, fully qualify the field reference by adding a table name. For example:

SELECT Orders.OrderID

FROM Orders, [Order Details];


Joined table <name> not listed in FROM clause. (Error 3080)

Add the specified table name to the FROM clause of the query, and then try the operation again.


Can't join more than one table with the same name <name>. (Error 3081)

You tried to join two or more tables that have the same name. Select different tables, rename one of the tables, or use an alias, and then try the operation again. If you are trying to join a table to itself, use a table alias to change the second reference to the table.


JOIN operation <operation> refers to a field that isn't in one of the joined tables. (Error 3082)

You tried to execute an SQL statement that contains an invalid join. This error occurs when you try to create a join on a field that isn't in one of the joined tables. The following example produces this error.

SELECT Authors.FirstName, Titles.ISBN

FROM Authors, Titles, AuthorTitles,

Authors INNER JOIN Titles ON Authors.ID = AuthorTitles.ISBN;

The error occurs because the join involves the Authors and Titles tables, but the joined fields are in the Authors and AuthorTitles tables.


Can't use internal report query. (Error 3083)

You tried to use an SQL statement that includes an explicit reference to a disallowed internal report query. Remove the invalid reference and then try the operation again.


Can't insert data with action query. (Error 3084)

You tried to run an append query using an action query for the input. Replace the action query with a select query and then try the operation again.


Undefined function <name> in expression. (Error 3085)

You entered an SQL expression that includes a Function procedure name that can't be recognized. Make sure the function exists, that it can be used in SQL expressions, or check the expression to make sure you entered the name correctly.


Couldn't delete from specified tables. (Error 3086)

You tried to delete data from one or more tables, but the deletion couldn't be completed.

Possible causes:

•	You don't have permission to modify the table. To change your permissions assignments, see your system administrator or the table's creator.

•	The database was opened for read-only access. The database is read-only for one of these reasons:

•	You used the OpenDatabase method and opened the database for read-only access.

•	The database file is defined as read-only in the database server operating system or by your network.

•	In a network environment, you don't have write privileges for the database file.

•	In Visual Basic, you used the Data control and set the ReadOnly property to True.

To delete the data, close the database, resolve the read-only condition, and then reopen the file for read/write access.


Too many expressions in GROUP BY clause. (Error 3087)

You created an SQL statement with more than 10 fields listed in the GROUP BY clause. Remove some of the fields listed in the GROUP BY clause.


Too many expressions in ORDER BY clause. (Error 3088)

You created an SQL statement that has an ORDER BY clause with more than ten expressions. Remove some of the fields listed in the ORDER BY clause.


Too many expressions in DISTINCT output. (Error 3089)

You created an SQL statement that has an ALL, DISTINCT, or DISTINCTROW predicate with more than ten expressions. Remove the DISTINCT reserved word, or remove some of the fields listed in the DISTINCT predicate.


Resultant table not allowed to have more than one AutoNumber field. (Error 3090)

You tried to execute a query that would result in a table with more than one field that has an AutoNumber data type. Change the query to include only one AutoNumber field.


Can't use HAVING clause in TRANSFORM statement. (Error 3092)

If you want to specify selection criteria, use a WHERE clause.


ORDER BY clause <clause> conflicts with DISTINCT. (Error 3093)

You created an SQL statement with an ALL, DISTINCT, or DISTINCTROW predicate and an ORDER BY clause that contains a field not listed in the SELECT statement. Remove the DISTINCT reserved word, or remove the specified field from the ORDER BY clause.


ORDER BY clause <clause> conflicts with GROUP BY clause. (Error 3094)

This error can occur when you create a select query and specify grouped fields after sorted fields that are not grouped. For example, you created an SQL statement with the specified field out of sequence in the ORDER BY clause. Move the specified field to the left of the ungrouped fields, or remove the specified field from the ORDER BY clause.


Can't have aggregate function in expression <expression>. (Error 3095)

You can't use an aggregate function in this expression.


Can't have aggregate function in WHERE clause <clause>. (Error 3096)

You can't use an aggregate function in the WHERE clause of an SQL statement.


Can't have aggregate function in ORDER BY clause <clause>. (Error 3097)

You can't use an aggregate function in the ORDER BY clause of an SQL statement.


Can't have aggregate function in GROUP BY clause <clause>. (Error 3098)

You can't use an aggregate function in the GROUP BY clause of an SQL statement.


Can't have aggregate function in JOIN operation <operation>. (Error 3099)

You can't use an aggregate function in the JOIN operation of an SQL statement.


Can't set field <name> in join key to Null. (Error 3100)

You have a join, and you tried to set a field on either side of the join to a Null value. Either select different fields or enter data in the fields, and then try the operation again.


The Microsoft Jet database engine can't find a record in the table <name> with key matching field(s) <name>. (Error 3101)

In a one-to-many relationship, you entered data on the "many" side for which there is no matching record on the "one" side. For example, this error occurs if you join a Customers table and Orders table on a CustomerID field, and then add an order using a CustomerID that doesn't exist in the Customers table.


Circular reference caused by <query reference>. (Error 3102)

You tried to execute a query that depends on itself for data. For example, this error occurs if you execute either of the following queries:

Query1

SELECT * FROM Employees, Query2;

Query2

SELECT * FROM Query1;

Redesign the queries to eliminate the dependency.


Circular reference caused by alias <name> in query definition's SELECT list. (Error 3103)

The specified alias created a reference that can't be resolved. This error can occur, for example, if you enter the following SQL statement, in which A is the circular reference:

SELECT A + B AS C, C + D AS E, E + F AS A
FROM MyTable;

SELECT week1 + week2 as hours, hours + overtime as gross, gross + ytdpay as week1

FROM EmployeePay


Can't specify fixed column heading <value> in a crosstab query more than once. (Error 3104)

When you create a crosstab query with fixed column headings, the values you specify must be unique. Change one or more of the duplicate column headings, and then try the operation again.


Missing destination field name in SELECT INTO statement <statement>. (Error 3105)

Enter a destination field name in the specified statement, and then try the operation again.


Missing destination field name in UPDATE statement <statement>. (Error 3106)

Enter a destination field name in the specified statement, and then try the operation again.


Record(s) can't be added; no insert permission on <name>. (Error 3107)

You must have insert data permission for the specified table or query to insert data into it. To change your permission assignments, see your system administrator or the table or query's creator.


Record(s) can't be edited; no update permission on <name>. (Error 3108)

You must have update data permission for the specified table or query to replace data in it. To change your permission assignments, see your workgroup administrator or the table or query's creator.


Record(s) can't be deleted; no delete permission on <name>. (Error 3109)

You must have delete permission for the specified table or query in order to delete data. To change your permission assignments, see your system administrator or the table or query's creator.


Couldn't read definitions; no read definitions permission for table or query <name>. (Error 3110)

You must have read definitions permission for the specified table or query to read its definition. To change your permission assignments, see your system administrator or the table or query's creator.


Couldn't create; no modify design permission for table or query <name>. (Error 3111)

You tried to create the specified table or query, but you don't have the required modify design permission. To change your permission assignments, see your system administrator or the query's creator.


Record(s) can't be read; no read permission on <name>. (Error 3112)

You must have read permission for the specified table or query to view its data. To change your permission assignments, see your system administrator or the table or query's creator.


Can't update <field name>; field not updatable. (Error 3113)

Possible causes:

•	The specified field is part of a TableDef or dynaset-type Recordset object that can't be updated. For example, this error occurs if you try to update an AutoNumber field.

•	You executed a query that combines updatable and nonupdatable TableDef objects, and you tried to update one of the fields in the query's results (the resulting dynaset-type Recordset).


Can't include Memo or OLE Object when you select unique values <statement>. (Error 3114)

Remove the DISTINCT reserved word or the Memo or OLE Object field from the statement.


Can't have Memo or OLE Object fields in aggregate argument <statement>. (Error 3115)

You can't include Memo or OLE Object fields in an aggregate function.


Can't have Memo or OLE Object fields in criteria <criteria> for aggregate function. (Error 3116)

The HAVING clause of an SQL statement can't include Memo or OLE Object fields.


Can't sort on Memo or OLE Object <clause>. (Error 3117)

The ORDER BY clause of an SQL statement can't include Memo or OLE Object fields.


Can't join on Memo or OLE Object <name>. (Error 3118)

You can't join Memo or OLE Object fields. The field you use to logically tie two or more tables together must be some other data type, such as text or integer.


Can't group on Memo or OLE Object <clause>. (Error 3119)

The GROUP BY clause of an SQL statement can't include Memo or OLE Object fields.


Can't group on fields selected with '*' <table name>. (Error 3120)

You tried to execute a SELECT statement that groups or totals all fields in a single table, selected with an asterisk ( * ). This error occurs, for example, if you enter the following SQL statement:

SELECT Orders.* FROM Orders GROUP BY ShipVia;


Can't group on fields selected with '*'. (Error 3121)

You tried to execute a SELECT statement that groups or totals all fields from all tables, selected with an asterisk ( * ).

Possible cause:

•	You created an SQL statement that includes an aggregate function or GROUP BY clause that refers to a field you selected with an asterisk. This error occurs, for example, if you enter the following SQL statement:

SELECT * FROM Orders GROUP BY ShipVia;


You tried to execute a query that doesn't include the specified expression <name> as part of an aggregate function. (Error 3122)

You tried to execute a query that doesn't include the specified expression as part of an aggregate function or grouping.

Possible cause:

•	You didn't enter an aggregate function in the TRANSFORM statement.


Can't use '*' in crosstab query. (Error 3123)

You tried to execute a query that groups or totals fields selected with an asterisk ( * ). Choose specific fields, and then try the operation again.


Can't input from internal report query <name>. (Error 3124)

You tried to use an SQL statement that includes an explicit reference to a disallowed internal report query.


The database engine can't find <name>. Make sure it is a valid parameter or alias name, that it doesn't include invalid characters or punctuation, and that the name isn't too long. (Error 3125)

The specified name doesn't follow standard naming conventions or isn't a valid parameter or alias name. Check your entry to make sure you haven't included invalid characters or punctuation and that the name isn't too long.


Invalid bracketing of name <name>. (Error 3126)

The specified name either can't have brackets around it or the brackets are mismatched. Check your entry to make sure the brackets are properly matched, and then try the operation again.


The INSERT INTO statement contains the following unknown field name: <field name>. Make sure you've typed the name correctly, and try the operation again.(Error 3127)

You tried to use an INSERT INTO statement with the specified field name, but that field doesn't exist in the output table. Make sure you've typed the name correctly, and then try the operation again.


Specify the table containing the records you want to delete. (Error 3128)

You tried to execute a delete query but the query doesn't specify the name of the table containing the records you want to delete.

Possible cause:

•	You didn't type an asterisk for each table in the ALL, DISTINCT, DISTINCTROW predicates. Instead, you typed field names (for example, Customers.Address instead of Customers.*).


Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'. (Error 3129)

Your SQL statement couldn't be recognized because it doesn't begin with one of the specified reserved words.


Syntax error in DELETE statement. (Error 3130)

You entered an SQL statement that has an invalid DELETE statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in FROM clause. (Error 3131)

You entered an SQL statement that has an invalid FROM clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in GROUP BY clause. (Error 3132)

You entered an SQL statement that has an invalid GROUP BY clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in HAVING clause. (Error 3133)

You entered an SQL statement that has an invalid HAVING clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in INSERT INTO statement. (Error 3134)

You entered an SQL statement that has an invalid INSERT INTO statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in JOIN operation. (Error 3135)

You entered an SQL statement that has an invalid join operation. It could be an inner join, outer join, or self-join.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


The LEVEL clause includes a reserved word or argument that is misspelled or missing, or the punctuation is incorrect. (Error 3136)

You entered an SQL statement that has an invalid reserved word clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in ORDER BY clause. (Error 3138)

You entered an SQL statement that has an invalid ORDER BY clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in PARAMETER clause. (Error 3139)

You entered an SQL statement with an invalid PARAMETERS declaration.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in PROCEDURE clause. (Error 3140)

You entered an SQL statement that has an invalid PROCEDURE clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect. (Error 3141)

You entered an SQL statement that has an invalid SELECT statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in TRANSFORM statement. (Error 3143)

You entered an SQL statement that has an invalid TRANSFORM statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in UPDATE statement. (Error 3144)

You entered an SQL statement that has an invalid UPDATE statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in WHERE clause. (Error 3145)

You entered an SQL statement that has an invalid WHERE clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


ODBC - call failed. (Error 3146)
ODBC – call failed. (Error 3146)

Using an ODBC connection, you tried to perform an operation on data in an ODBC data source. This error may occur when the ODBC data source is on a network drive and you aren't connected to the network. Make sure the network is available, and then try the operation again.


ODBC ¾ connection to <name> failed. (Error 3151)
ODBC — connection to <name> failed. (Error 3151)

The ODBC connection to the specified ODBC database or table couldn't be made. If the ODBC database is accessed via a network connection, make sure the network is available, and then try the operation again.


ODBC ¾ couldn't find DLL <name>. (Error 3154)
ODBC — couldn't find DLL <name>. (Error 3154)

Using an ODBC connection, you tried to perform an operation that requires the specified DLL.

Possible causes:

•	The DLL file is on a network drive and the network isn't connected. Make sure the network is available, and then try the operation again.

•	The DLL file wasn't installed properly. Reinstall the ODBC driver, and then try the operation again.


ODBC ¾ insert on a linked table <table> failed. (Error 3155)
ODBC — insert on a linked table <table> failed. (Error 3155)

Using an ODBC connection, you tried to insert data into an ODBC database; that insertion couldn't be completed.

Possible causes:

•	The insertion would have caused a rule violation.

•	The ODBC database is read-only, or you don't have permission to insert data in that database. Resolve the read-only condition, or see your system administrator or the person who created the database to obtain the necessary permissions.

•	The ODBC database is on a network drive, and you aren't connected to the network. Make sure the network is available, and then try the operation again.


ODBC ¾ delete on a linked table <table> failed. (Error 3156)
ODBC — delete on a linked table <table> failed. (Error 3156)

Using an ODBC connection, you tried to delete data from an ODBC database; the deletion couldn't be completed.

Possible causes:

•	The deletion would have caused a rule violation.

•	The ODBC database is read-only, or you don't have permission to delete data in that database. Resolve the read-only condition, or see your system administrator or the person who created the database to obtain the necessary permissions.

•	The ODBC database is on a network drive and the network isn't connected. Make sure the network is available, and then try the operation again.


ODBC ¾ update on a linked table <table> failed. (Error 3157)
ODBC — update on a linked table <table> failed. (Error 3157)

Using an ODBC connection, you tried to update data in an ODBC database; that update couldn't be completed.

Possible causes:

•	The update would have caused a rule violation.

•	The ODBC database is read-only, or you don't have permission to update data in that database. Resolve the read-only condition, or see your system administrator or the person who created the database to obtain the necessary permissions.

•	The ODBC database is on a network drive and the network isn't connected. Make sure the network is available, and then try the operation again.


Couldn't save record; currently locked by another user. (Error 3158)

You tried to save a record that is on a database page currently locked by another user. To save your changes, wait for the other user to finish working with the record, and then try the operation again.


Not a valid bookmark. (Error 3159)

You tried to set a bookmark to an invalid string.

This error can occur if you set the Bookmark property to a string that is invalid or wasn't saved from previously reading a Bookmark property. For example, the following code produces this error:

Sub SetBookmark()

Dim dbs As Database

Dim rstEmployees As Recordset

Dim strPlaceholder As String

Set dbs = OpenDatabase("Northwind.mdb")

Set rstEmployees = _

dbs.OpenRecordset _

("Employees", dbOpenDynaset)

strPlaceholder = "1"

rstEmployees.Bookmark = strPlaceholder	' Not a valid bookmark.

End Sub


Table isn't open. (Error 3160)

You tried to perform an operation on a table that hasn't been opened. Open the table, and then try the operation again.


Couldn't decrypt file. (Error 3161)

You tried to access an encrypted Btrieve or Paradox table, but the password you provided isn't correct. Try the operation again and enter the correct password.


You tried to assign the Null value to a variable that isn't a Variant data type. (Error 3162)

You tried to assign a Null value to a variable that isn't a Variant data type. Use the Dim statement to declare the variable as a Variant, and then try the operation again.


The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data. (Error 3163)

The field into which you tried to insert or paste data isn't large enough to hold the data. Try inserting or pasting less data.


The field can't be updated because another user or process has locked the corresponding record or table. (Error 3164)

Possible causes:

•	You tried to update a field in a record or table that is currently locked by another user. Wait for the other user to finish working with the record or table, and then try the operation again.

•	In Microsoft Access, you tried to change the value of a control whose Locked property is set to Yes.


Couldn't open .inf file. (Error 3165)

You tried to link a dBASE table, but the associated .inf file that contains index information about that table could not be opened or created.

Possible causes:

•	There isn't enough disk space available to create the .inf file.

•	In a network environment, you don't have write privileges for the network drive.


Cannot locate the requested Xbase memo file. (Error 3166)

You tried to access a dBASE (.dbf) file, but the file's associated memo (.dbt) file couldn't be found. Make sure the .dbt file is in the same directory as the .dbf file, and then try the operation again.


Record is deleted. (Error 3167)

You referred to a record that you deleted or that another user in a multiuser environment deleted. Move to another record, and then try the operation again.


Invalid .inf file. (Error 3168)

You tried to access a dBASE table, but its associated .inf file is invalid or has become corrupted. Relink the table, making sure you specify the correct indexes.


The Microsoft Jet database engine could not execute the SQL statement because it contains a field that has an invalid data type. (Error 3169)

You tried to execute an SQL statement that contains a field that has an invalid field data type.

Possible causes:

•	You included a Memo or OLE Object field in an expression where it isn't allowed.

•	You included a numeric aggregate function, such as Sum or StDev, that tried to perform a calculation on a Text field. Choose a different aggregate function.


Couldn't find installable ISAM. (Error 3170)

The DLL for an installable ISAM file couldn't be found. This file is required for linking external tables (other than ODBC or Microsoft Jet database tables). The locations for all ISAM drivers are maintained in the Windows Registry. These entries are created automatically when you install your application. If you change the location of these drivers, you need to correct your application Setup program to reflect this change and make the correct entries in the Registry.

Possible causes:

•	An entry in the Registry isn't valid. For example, this error occurs if you're using a Paradox external database, and the Paradox entry points to a nonexistent directory or driver. Exit the application, correct the Windows Registry, and try the operation again.

•	One of the entries in the Registry points to a network drive and that network isn't connected. Make sure the network is available, and then try the operation again.


Couldn't find network path or user name. (Error 3171)

One or more entries in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Paradox key of the Windows Registry is invalid. Correct the invalid entries, and then try the operation again.


Couldn't open Paradox.net. (Error 3172)

Possible causes:

•	The ParadoxNetPath value in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Paradox Registry key isn't valid. This error occurs if you're using the Paradox external database, and the ParadoxNetPath value points to a nonexistent directory. Exit the application, correct the invalid entry, and try the operation again.

•	The ParadoxNetPath Registry value points to a network drive, and you aren't connected to that network drive. Make sure the network drive is available, and then try the operation again.


Couldn't open table 'MSysAccounts' in the workgroup information file. (Error 3173)

This operation requires the System.mdw file, which contains the security and option settings for Microsoft Jet database tables.

Possible causes:

•	The SystemDB value of the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\Jet\3.5\Engines\Jet key in the Windows Registry points to a network drive that isn't connected. Make sure the network drive is available, and then try the operation again.

•	The System.mdw file is corrupted. If you have a backup copy of System.mdw, copy it to the location specified in the SystemDB entry in the Registry.


Couldn't open table 'MSysGroups' in the workgroup information file. (Error 3174)

This operation requires the System.mdw file, which contains the security and option settings for Microsoft Jet database tables.

Possible causes:

•	The SystemDB value of the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\Access\Jet\3.5\Engines\Jet key in the Windows Registry points to a network drive that isn't connected. Make sure the network drive is available, and then try the operation again.

•	The System.mdw file is corrupted. If you have a backup copy of System.mdw, copy it to the location specified in the SystemDB entry in the Registry.


Date is out of range or is in an invalid format. (Error 3175)

Only dates from December 30, 1899, through December 30, 9999 are recognized.

Possible causes:

•	You entered a date that was outside the valid range.

•	You entered a valid date, but it wasn't in a recognized format. Make sure you entered it correctly, and then try the operation again.


Couldn't open file <name>. (Error 3176)

The specified text or spreadsheet file couldn't be opened. The specified file specification may be invalid, another user may be accessing the file, or you may not have read privileges for the file. Wait for the other user to finish using the file and then try the operation again, or contact your system administrator or network administrator.


Not a valid table name. (Error 3177)

The name you entered doesn't follow standard naming conventions. Enter a new name, and then try the operation again.


Encountered unexpected end of file. (Error 3179)

You tried to import a file that contains an end-of-file marker in an unexpected position.

Possible causes:

•	The import file is corrupted. Restore a backup copy of the import file, and then try the operation again.

•	The import/export specifications you're using don't match the data in the import file. Edit the import/export specifications, and then try the operation again.


Couldn't write to file <name>. (Error 3180)

You tried to export data to the specified text or spreadsheet file, but the file couldn't be modified.

Possible causes:

•	Another user is currently accessing the file. Wait for the other user to finish using the file and then try the operation again.

•	The file has been defined as read-only in the operating system or by your network. Resolve the read-only condition and then try the operation again.

•	In a network environment, you don't have write privileges for the file.

You may need to contact your system administrator or network administrator.


Invalid range. (Error 3181)

You attempted to import an invalid range of spreadsheet cells.


Invalid file format. (Error 3182)

Possible causes:

•	The file you tried to read or link is corrupted. Restore a backup copy of the file to your disk, and then try the operation again.

•	The file format is not recognized. If the file is a Btrieve, dBASE, or Paradox file, run Setup to install the installable ISAM, and then link the file.


Not enough space on temporary disk. (Error 3183)

You tried to perform an operation that requires more space than is available on the temporary disk. Your temporary disk location is based on the TEMP DOS environment variable, which was set when your system started.

For example, you may be trying to create a query that creates temporary files larger than the temporary disk. Reduce the size of the temporary files by accessing smaller amounts of data at one time or increase the size of the temporary disk.

You can increase the amount of available temporary disk space in several ways:

•	Select fewer records. Dynaset-type, forward-only – type, and snapshot-type Recordset objects record keys and data to the temporary disk.

•	Select a different drive for your temporary disk.

•	If the temporary disk is a RAM disk, increase the amount of available RAM and the space allocated to the RAM disk, or move it to a fixed disk.

•	Free some space by deleting data or by removing unneeded tables, queries, forms, macros, and modules from your database.

•	Free some space by compressing deleted records out of your database.

•	If you still need additional space, consider removing other unused files from your disk.


Couldn't execute query; couldn't find linked table. (Error 3184)

Possible causes:

•	The linked table no longer exists or has been renamed or moved. Link the table and then try to execute the query again.

•	The linked table is on a network drive, and you aren't connected to the network. Make sure the network is available, and then try to execute the query again.


SELECT INTO on a remote database tried to produce too many fields. (Error 3185)

The Microsoft Jet database supports up to 255 fields per table, but the other database supports fewer fields. A SELECT...INTO statement created a table with more fields than the remote database can support. Reduce the number of columns produced by the SELECT INTO statement, and then try the operation again.


Couldn't save; currently locked by user <name> on machine <name>. (Error 3186)

Possible causes:

•	You tried to save a record on a 2K database page that is currently locked by another user. Wait for the other user to finish working with the record, and then try the operation again.


Couldn't read; currently locked by user <name> on machine <name>. (Error 3187)

You tried to read information on a database page that is currently locked by the specified user. Wait for the other user to finish, and then try the operation again.


Couldn't update; currently locked by another session on this machine. (Error 3188)

You tried to update information that is currently locked by another session. Wait for the other session to finish or close the other session, and then try the operation again.


Table <name> is exclusively locked by user <name> on machine <name>. (Error 3189)

You can't access the specified table because it is exclusively locked by another user. Contact the other user, or wait for the other user to release the lock, and then try the operation again.


Too many fields defined. (Error 3190)

You tried to perform an operation that involves more than 255 fields. Reduce the number of fields, and then try the operation again.


Can't define field more than once. (Error 3191)

You tried to create a table in which more than one field was defined with the same name. Each field name in a table must be unique.


Couldn't find output table <name>. (Error 3192)

You tried to use an INSERT INTO statement with the specified table, which doesn't exist. Make sure you entered the name correctly, and then try the operation again.

If you're attempting to execute a make table query that creates the table for you, use the SELECT INTO syntax instead.


The database <database name> is already in use by another person or process. When the database is available, try the operation again. (Error 3196)

The specified database is currently being used exclusively by another user or session. Wait for the other user or session to finish working with the database, and then try the operation again.


The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time. (Error 3197)

This error can occur in a multiuser environment.

Another user has changed the data you are trying to update. This error can occur when multiple users open a table or create a Recordset and use optimistic locking. Between the time you used the Edit method and the Update method, another user changed the same data.

To overwrite the other user's changes with your own, execute the Update method again.


Couldn't start session.  Too many sessions already active. (Error 3198)

You tried to perform an operation that would have started a new session, but too many sessions are already active. Wait for one or more sessions to finish, and then try the operation again.


Couldn't find reference. (Error 3199)

You entered a file, table, or field reference that couldn't be found. Check the spelling and punctuation to make sure you entered the reference correctly, and then try the operation again.


The record cannot be deleted or changed because table <name> includes related records. (Error 3200)

You tried to perform an operation that would have violated referential integrity rules for related tables. For example, this error occurs if you try to delete or change a record in the "one" table in a one-to-many relationship when there are related records in the "many" table.

If you want to delete or change the record, first delete the related records from the "many" table.


You can't add or change a record because a related record is required in table <name>. (Error 3201)

You tried to perform an operation that would have violated referential integrity rules for related tables. For example, this error occurs if you try to change or insert a record in the "many" table in a one-to-many relationship, and that record doesn't have a related record in the table on the "one" side.

If you want to add or change the record, first add a record to the "one" table that contains the same value for the matching field.


Couldn't save; currently locked by another user. (Error 3202)

Possible causes:

•	You tried to save a record on a 2K database page that is currently locked by another user. Wait for the other user to finish working with the record, and then try the operation again.


Subqueries cannot be used in the expression <expression>. (Error 3203)

The specified expression contains a subquery or other expression that functions as a subquery.

Possible cause:

•	You used a SELECT statement that includes an aggregate function that evaluates another aggregate function. This error occurs, for example, if you execute the following statement:

TRANSFORM Sum([OrderAmount]) AS Sum1

SELECT Sum([Sum1]) AS Sum2, OrderID, Sum([Sum2]) AS Expr1

FROM Orders

GROUP BY OrderID

PIVOT ShipName;

The <expression> parameter of the alert would contain the expression Sum([Sum2]) from the SELECT clause, because this references an alias used in the same SELECT statement and acts as a subquery against Sum([Sum1]).


Database already exists. (Error 3204)

You tried to create or rename a database using a name that already exists. Enter a different name, and then try the operation again.


Too many crosstab column headers <value>. (Error 3205)

You executed an SQL statement that tried to create too many columns. The specified value is the column that produced this error.

You can reduce the number of columns by adding additional conditions to the WHERE clause or, if there is no WHERE clause, add one.


Can't create a relationship between a field and itself. (Error 3206)

You tried to create a relationship between a field and itself. Choose a different field for the primary or related table, and then try the operation again.


Operation not supported on a Paradox table with no primary key. (Error 3207)

Run the application that created the table, and add a primary key. Then, try the operation again.


Invalid Deleted setting in the Xbase key of the Windows Registry. (Error 3208)

There is an invalid Deleted setting in the Xbase key of the Windows Registry.

To fix the Deleted setting

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key, and select the Deleted value.

3	On the Edit menu, click Modify.

4	Correct the Deleted data in the Value data box.

5	Restart your application, and then try the operation again.


The connection string is too long. (Error 3210)

The connection string in the IN clause of an SQL statement can't be longer than 255 characters. Correct your entry, and then try the operation again.


The database engine couldn't lock table <name> because it's already in use by another person or process. (Error 3211)

To complete this operation, a table currently in use by another user must be locked. Wait for the other user to finish working with the table, and then try the operation again.


Couldn't lock table <name>; currently in use by user <name> on machine <name>. (Error 3212)

The table can't be locked because it is currently in use. Wait for the other user's transaction to complete, and then try the operation again.


Invalid Date setting in the Xbase key of the Windows Registry. (Error 3213)

There is an invalid Date setting in the Xbase key of the Windows Registry.

To fix the Date setting

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key, and select the Date value.

3	On the Edit menu, click Modify.

4	Correct the Date data in the Value data box.

5	Restart your application, and then try the operation again.


Invalid Mark setting in the Xbase key of the Windows Registry. (Error 3214)

There is an invalid Mark setting in the Xbase key of the Windows Registry.

To fix the Mark setting

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key, and select the Mark value.

3	On the Edit menu, click Modify.

4	Correct the Mark data in the Value data box.

5	Restart your application, and then try the operation again.


Too many Btrieve tasks. (Error 3215)

Too many applications are using the Btrieve driver. In a multiuser environment, this error can occur when too many users access the same server. Contact your system administrator or network administrator.


Parameter <name> specified where a table name is required. (Error 3216)

You created a parameter query that specifies an invalid parameter type. The following example produces this error.

PARAMETERS Param1 Text;

INSERT INTO Param1

SELECT *

FROM Customers;

Param1 is a text parameter, but the INSERT INTO statement expects a table name.

Change the parameter type from Text to TableID, and then try the operation again.


Parameter <name> specified where a database name is required. (Error 3217)

You created a parameter query that specifies an invalid parameter type. The following example produces this error:

PARAMETERS Param1 Text;

SELECT CustomerID

FROM Customers IN Param1;

Param1 is a text parameter, but the FROM clause requires a database parameter.

Change the parameter type from Text to Database, and then try the operation again.


Couldn't update; currently locked. (Error 3218)

You tried to update data that is located on a page that is currently locked.

Possible causes:

•	You tried to save a query that is being used by someone else. To save your query, wait for the other user to finish or enter a different name, and then try the operation again.

•	You tried to use the Edit method on a data page containing a record that is already open or locked.


Invalid operation. (Error 3219)

Possible causes:

•	You tried to write to a read-only property. See the Help topic for the property to determine whether it is read/write.

•	You tried to use a method or property on a type of Recordset object that the method or property doesn't apply to. See the Recordset object Summary topic to determine which methods and properties apply to a given type of Recordset object.

•	You tried to append a property to a Properties collection of an object that doesn't support user-defined properties.

•	You tried to use the Update method on a read-only Recordset object.


Incorrect collating sequence. (Error 3220)

You tried to link a Paradox table that was created with an international sort order that isn't the same as the one you are using.


Invalid settings in the Btrieve key of the Windows Registry. (Error 3221)

A setting in the Btrieve key of the Windows Registry isn't valid. For example, this error occurs if the /l: or /f: settings in the options entry are invalid.

To fix the Windows Registry settings

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Btrieve key, and select the value that needs to be fixed.

3	On the Edit menu, click Modify.

4	Correct the data in the Value data box.

5	Restart your application, and then try the operation again.


Query can't contain a Database parameter. (Error 3222)

Change the parameter field data type for this parameter query to a valid field data type, and then try the operation again.


<Parameter name> is invalid because it's longer than 64 characters or contains invalid characters. (Error 3223)

The parameter name is longer than 64 characters or contains invalid characters. Correct the name, and then try the operation again.


Can't read Btrieve data dictionary. (Error 3224)

Restore a backup copy of the DDF file, and then try the operation again.


Encountered a record locking deadlock while performing a Btrieve operation. (Error 3225)

You tried to lock a record during an update, insert, or delete operation on a linked Btrieve table, and another user is also trying to lock the same record. Cancel the operation, wait for the other user to finish, and then try the operation again.


Errors encountered while using the Btrieve DLL. (Error 3226)

An unexpected error occurred when you tried to access data in a linked Btrieve table. Try the operation again, or contact your system administrator or network administrator.


Invalid Century setting in the Xbase key of the Windows Registry. (Error 3227)

There is an invalid Century setting in the Xbase key of the Windows Registry.

To fix the Century setting

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key, and select the Century value.

3	On the Edit menu, click Modify.

4	Correct the Century data in the Value data box.

5	Restart your application, and then try the operation again.


Invalid CollatingSequence setting in the Paradox key of the Windows Registry. (Error 3228)

There is an invalid CollatingSequence setting in the Paradox key of the Windows Registry.

To fix the CollatingSequence setting

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Paradox key, and select the CollatingSequence value.

3	On the Edit menu, click Modify.

4	Specify either ascii or International in the Value data box.

5	Restart your application, and then try the operation again.


Btrieve ¾ can't change field. (Error 3229)
Btrieve — can't change field. (Error 3229)

You tried to update a field in a Btrieve table that is part of an index that can't be modified. Use Novell Xtrieve or another program to change the attribute of the index that can't be modified, and then try the operation again.


Out-of-date Paradox lock file. (Error 3230)

You tried to use a Paradox table, but the table's associated lock (.lck) file is outdated. Delete the .lck file and then try the operation again.


ODBC ¾ field would be too long; data truncated. (Error 3231)
ODBC — field would be too long; data truncated. (Error 3231)

You tried to perform a task on an ODBC data source that would have resulted in a field that is too long. The data has been truncated to the maximum allowable length.


ODBC ¾ couldn't create table. (Error 3232)
ODBC — couldn't create table. (Error 3232)

You tried to export a table to an ODBC database and the table couldn't be created. This error can occur if the ODBC database is read-only, or you don't have permission to create a table in that database. Resolve the read-only condition, or see your system administrator or the person who created the database to obtain the necessary permissions.


ODBC ¾ remote query timeout expired. (Error 3234)
ODBC — remote query timeout expired. (Error 3234)

The ODBC server may not be properly installed, or a required network connection isn't active. Try increasing the value of the QueryTimeout property.


ODBC ¾ data type not supported on server. (Error 3235)
ODBC — data type not supported on server. (Error 3235)

The ODBC server doesn't support the same SQL data types as the database engine or your application. The data has not been placed on the server.


ODBC ¾ data out of range. (Error 3238)
ODBC — data out of range. (Error 3238)

Using an ODBC connection, you tried to read from or write to an ODBC database, and the data isn't within the prescribed limits.


Too many active users. (Error 3239)

In a multiuser environment, Microsoft Jet databases support up to 255 concurrent users. Wait for one or more users to stop using the system, and then try the operation again.


Btrieve ¾ missing Btrieve engine. (Error 3240)
Btrieve — missing Btrieve engine. (Error 3240)

You tried to perform an operation that requires the specified file. To use DAO to read and write data to a Btrieve file, you must have a copy of the stand-alone Btrieve for Windows engine. This file must be in your \Windows\System directory.

If you don't have a copy of this file, you can purchase Btrieve for Windows by contacting your local software dealer.


Btrieve ¾ out of resources. (Error 3241)
Btrieve — out of resources. (Error 3241)

While working with a Btrieve file, your application ran out of resources.

To increase the number of resources

1	Exit your application.

2	Start the Registry Editor, and navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Btrieve key.

3	Increase one or more settings in the Btrieve key of the Windows Registry.

4	Restart your application, and then try the operation again.

For more information, refer to your Btrieve documentation.


Invalid reference in SELECT statement. (Error 3242)

You entered an invalid field or table reference in the SELECT statement. For example, the reference may be misspelled or doesn’t exist.


None of the import field names match fields in the appended table. (Error 3243)

At least one field name in the import table and the appended table must match.


Can't import password-protected spreadsheet. (Error 3244)

Return to the application that was used to save the spreadsheet, save the spreadsheet again without a password, and then try to import the spreadsheet again.


Couldn't parse field names from the first row of the import table. (Error 3245)

The first row of data contains invalid field names, such as quoted and unquoted strings in the same field name. In the following example, the third and fourth field names can't be parsed:

"Name", Date, "ID " Number, Phone" Number"

The first two fields are valid, but the third and fourth aren't because they contain nonspace characters outside the quotation marks.

Check the import table for properly matched quotation marks, and then try the import operation again


Operation not supported in transactions. (Error 3246)

You tried to perform an operation that isn't valid within a transaction. A transaction can be one you create using a BeginTrans statements, or an internal transaction created by the Microsoft Jet database engine, such as when you delete multiple records in a single operation.


ODBC ¾ linked table definition has changed. (Error 3247)
ODBC — linked table definition has changed. (Error 3247)

The definition or structure of a linked table changed since you created the link. Delete the link, and then relink the table.


Invalid NetworkAccess setting in the Windows Registry. (Error 3248)

There is an invalid NetworkAccess setting in the Windows Registry.

To complete this operation

1	Exit your application.

2	Start the Registry Editor, and navigate to the NetworkAccess value.

Depending on which installable ISAM you're trying to use, the invalid entry is in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Btrieve or \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key.

3	On the Edit menu, click Modify.

4	Specify either On or Off in the Value data box.

5	Restart your application, and then try the operation again.


Invalid PageTimeout setting in the Windows Registry. (Error 3249)

There is an invalid PageTimeout setting in the Windows Registry.

To complete this operation

1	Exit your application.

2	Start the Registry Editor, and navigate to the PageTimeout value.

Depending on which installable ISAM you're trying to use, the invalid entry is in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Btrieve or \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Xbase key.

3	On the Edit menu, click Modify.

4	Specify a new value in the Value data box.

5	Restart your application, and then try the operation again.


Couldn't build key. (Error 3250)

When building a primary index, the Microsoft Jet database engine couldn't build a primary key. Make sure the key fields are named properly and that there are no duplicate records based on this key.

This error can occur when you use the Seek method and pass it a value for a field that is not part of the index. For example, suppose you want to use the Seek method on a Recordset whose current index uses the LastName field of the underlying table, and you write it this way:

rstEmployees.Seek "=", "Smith", "Joe"

Microsoft Jet will try to construct a primary key from two fields, but because one field is indexed, the attempt will fail and this error results.


Operation is not supported for this type of object. (Error 3251)

You were attempting to execute a method or assign a value to a property that is usually valid for the object, but isn't supported in this specific instance. For example, the Edit method is generally valid for Recordset objects, but not for a snapshot-type Recordset. This error could also occur in cases where the operation isn't permitted due to the type or status of the object — as when trying to use the MovePrevious method on a forward-only – type Recordset. Some operations are also not supported, depending on if you are accessing a Microsoft Jet or an ODBC data source.


Can't open a form whose underlying query contains a user-defined function that attempts to set or get the form's RecordsetClone property. (Error 3252)

This error can occur in Microsoft Access if you execute a query that includes a user-defined function in its output and then create a form based on that query.


ODBC ¾ Can't lock all records. (Error 3254)
ODBC — Can't lock all records. (Error 3254)

Using an ODBC connection, you tried to lock all of the records in an ODBC database.


Index file not found. (Error 3256)

You tried to access a dBASE table, but one of the indexes listed in the table's associated .inf file couldn't be found. The index may have been renamed, moved, or deleted. Either relink the table, or use Microsoft Windows Notepad or another text editor to update the .inf file.


Syntax error in WITH OWNERACCESS OPTION declaration. (Error 3257)

Possible causes:

•	The WITH OWNERACCESS OPTION declaration is incomplete or includes a space between OWNER and ACCESS.

•	The declaration appears in an unexpected and disallowed position in the SQL statement. For example:

SELECT * WITH OWNERACCESS OPTION FROM [My Table];

The WITH OWNERACCESS OPTION declaration should appear at the end of the SQL statement, usually after the ORDER BY clause, if present:

SELECT * FROM [My Table] WITH OWNERACCESS OPTION;


The SQL statement couldn't be executed because it contains ambiguous outer joins. To force one of the joins to be performed first, create a separate query that performs the first join and then include that query in your SQL statement. (Error 3258)

You tried to execute an SQL statement that contains multiple joins; the results of the query can differ depending on the order in which the joins are performed. For example, this error can occur if you execute the following SQL statement:

SELECT * FROM Customers, Orders, [Order Details],

Customers LEFT JOIN Orders

ON Customers.CustomerID = Orders.CustomerID,

Orders INNER JOIN [Order Details]

ON Orders.OrderID = [Order Details].OrderID;

Executing this statement produces an error because the order of the joins is ambiguous. To force one of the joins to be performed first, create a separate query that performs the first join and then include that query in your SQL statement. The following queries illustrate how you might construct the preceding query so that the INNER JOIN operation is performed before the LEFT JOIN and RIGHT JOIN operation:

Query1

SELECT * FROM Orders, [Order Details],

Orders INNER JOIN [Order Details]

ON Orders. OrderID = [Order Details].OrderID;

Query2

SELECT * FROM Customers, Query1,

Customers LEFT JOIN Query1

ON Customers.CustomerID = Orders.CustomerID;


Invalid field data type. (Error 3259)

The data type specified in the Field object's Type property isn't valid. Choose one of the valid types as shown in the Type property Help topic.


Couldn't update; currently locked by user <name> on machine <name>. (Error 3260)

You tried to update data that is located on a page that is currently locked.

Possible causes:

•	You tried to save a query being used by someone else. To save your query, wait for the other user to finish or enter a different name, and then try the operation again.

•	You tried to use the Edit method on a data page containing a record that is already open or locked.


Table <name> is exclusively locked by user <name> on machine <name>. (Error 3261)

You tried to use a table that is currently open for exclusive access by the specified user. Wait for the other user to finish working with the table, and then try the operation again.


Couldn't lock table <name>; currently in use by user <name> on machine <name>. (Error 3262)

You tried to lock a table while opening it, but the table can't be locked because it is currently in use. Wait a moment, and then try the operation again.


Invalid Database object. (Error 3263)

The Database object specified isn't the result of the OpenDatabase method, or it has been modified and is no longer valid.


No field defined ¾ cannot append TableDef or Index. (Error 3264)
No field defined — cannot append TableDef or Index. (Error 3264)

You can't append a TableDef until you define one or more fields. Use the CreateField method to create fields, append them to the Fields collection of your TableDef object, and then append the TableDef object to the TableDefs collection.


Item not found in this collection. (Error 3265)

An attempt to reference a name in a collection failed.

Possible causes:

•	The object doesn't exist in this collection. Make sure the object is appended to a collection before referencing it.

•	There is more than one object with this name in the collection; using its name is an ambiguous reference. Reference the object by its ordinal position in the collection (for example, Recordsets(3)).


Can't append a Field that is already a part of a Fields collection. (Error 3266).

A Field object was specified as an argument to an Append operation when it already is a member of an existing Fields collection. Use the Dim statement and CreateField method to declare a new Field object and specify its values, and retry the operation with the new Field object.


Property can be set only when the Field is part of a Recordset object's Fields collection. (Error 3267)

This property is valid only for Field objects that are part of a Recordset object's Fields collection. See the Field Object, Fields Collection Summary for a list of properties available for different Fields collections.


Can't set this property once the object is part of a collection. (Error 3268)

An attempt was made to change the value of a property of an object (TableDef, Field, and so on) that is already appended to a collection.


Can't append an Index that is already a part of an Indexes collection. (Error 3269)

An Index object was specified as an argument to an Append operation when it already is a member of an existing Indexes collection. Use the Dim statement and CreateIndex method to declare a new Index object and specify its values, and retry the operation with the new Index object.


Property not found. (Error 3270)

The specified property couldn't be found.

Possible causes:

•	The property doesn't exist. Check the spelling of the property in your code.

•	If the property is user-defined, it may have been deleted from the collection.


Invalid property value. (Error 3271)

Possible causes:

•	The setting for the Value property of the Parameter object is too long or is otherwise incorrect.

•	The Index object name is a zero-length string (" "). You must enter a name for the Index object when appending the object to the Indexes collection.

•	The Workspace object name is a zero-length string. You must enter a name for the Workspace object when appending the object to a Workspaces collection.


Object isn't a collection. (Error 3272)

You've referred to an object as though it were a collection. For example, a statement such as qrySales.Refresh or qrySales(2) causes this error.


Method not applicable for this object. (Error 3273)

You tried to use a method on an object that doesn't support that method. Refer to the Summary topic for the object to see a list of valid methods for that object.


External table isn't in the expected format. (Error 3274)

The format of the table has changed since it was linked. Link the table again, and then retry the operation.


Unexpected error from external database driver <error number>. (Error 3275)

The specified external database driver returned an error. This error can be caused by performing an operation not supported on this type of external database.


Invalid database object reference. (Error 3276)

The Database object specified isn't the result of the OpenDatabase method, or it has been modified and is no longer valid.


Can't have more than 10 fields in an index. (Error 3277)

You defined an index with more than ten fields. Reduce the number of fields to ten or less.


The Microsoft Jet database engine has not been initialized. (Error 3278)

The database engine cannot be initialized.

Possible causes:

•	There is a conflict with another application that uses the Microsoft Jet database engine. Quit all other applications, and then restart your application.

•	An error occurred during installation and setup. Reinstall your application.


The Microsoft Jet database engine has already been initialized. (Error 3279)

You attempted to initialize the Microsoft Jet database engine, but it has already been initialized.


Can't delete a field that is part of an index or is needed by the system. (Error 3280)

To delete a field that is part of an index, you must first delete the index.


Can't delete this index or table.  It is either the current index or is used in a relationship. (Error 3281)

If the index or table is used in a relationship, you must delete the relationship before you can delete the index or table. If the index is specified as the current index by the Index property, you must set the property to a different index before you can delete the index.


Operation not supported on a table that contains data. (Error 3282)

You can't add a field or create an index on a linked table that contains data. Once a table is populated with data, you can't change the table design or indexes. Create a new table with the altered design and transfer the data to it using an action query.


Primary key already exists. (Error 3283)

You're attempting to define a second primary key for this table. Each table can have only one primary key. Remove the reference to the second primary key.


Index already exists. (Error 3284)

You can't have two indexes with the same name in a table. Rename one of the indexes.


Invalid index definition. (Error 3285)

Possible causes:

•	You're using the same field twice in an index or relationship, which the Microsoft Jet database engine doesn't permit.

•	You're creating a relationship using fields with data types that don't match. In Microsoft Jet databases, you can only relate fields with identical data types or a AutoNumber field with a Number field set to a Long Integer.


Format of memo file doesn't match specified external database format. (Error 3286)

Your application can't read the memo file associated with the database you're trying to import or link and consequently can't import or link the file. The memo file may be in the wrong format; for example, if you selected dBASE IV as the data source and the memo file is in a FoxPro format.


Can't create index on the given field. (Error 3287)

You're trying to create an index on a Memo or OLE Object field. Specify another field, and then try the operation again.

This can also occur if you try to create an index on a Btrieve table on a 1-byte field.


Paradox index is not primary. (Error 3288)

You are attempting to create an index on a Paradox table for which no other indexes are defined. The first index created on a Paradox table must be a primary index.

Possible solutions:

•	Redefine the index as the primary index.

•	If the index you're attempting to create isn't the primary index, create the primary index first.


Syntax error in CONSTRAINT clause. (Error 3289)

You entered an SQL statement that includes an invalid CONSTRAINT clause.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in CREATE TABLE statement. (Error 3290)

You entered an SQL statement that includes an invalid CREATE TABLE statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in CREATE INDEX statement. (Error 3291)

You entered an SQL statement that includes an invalid CREATE INDEX statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in field definition. (Error 3292)

A syntax error occurred in the field definition of a CREATE TABLE or ALTER TABLE statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in ALTER TABLE statement. (Error 3293)

You entered an SQL statement that includes an invalid ALTER TABLE statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in DROP INDEX statement. (Error 3294)

You entered an SQL statement that has an invalid DROP INDEX statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Syntax error in DROP TABLE or DROP INDEX. (Error 3295)

You entered an SQL statement that has an invalid DROP statement.

Possible causes:

•	A reserved word or argument name is misspelled or missing.

•	Punctuation is incorrect.


Join expression not supported. (Error 3296)

Possible causes:

•	Your SQL statement contains multiple joins in which the results of the query can differ, depending on the order in which the joins are performed. You may want to create a separate query to perform the first join, and then include that query in your SQL statement.

•	The ON statement in your JOIN operation is incomplete or contains too many tables. You may want to put your ON expression in a WHERE clause.


Couldn't import table or query. No records found, or all records contain errors. (Error 3297)

The Microsoft Jet database engine couldn’t find the table or query you tried to import, or no records were found at the specified source, or all records contained errors. Check the path you specified and try it again.


There are several tables with that name. Please specify owner in the format 'owner.table'. (Error 3298)

More than one table with that name exists in the remote ODBC data source. To resolve the ambiguity, specify the owner of the table you want to access, using the owner.table syntax.


ODBC Specification Conformance Error <message>. Report this error to the developer of your application. (Error 3299)

This error can be caused by any of a number of problems with your ODBC driver. Write down the error number indicated in the message and report it to the developer of the application, who can then report it to the driver vendor.


Can't create a relationship. (Error 3300)

You are attempting to create a relationship that isn't allowed. For example, the tables may be in different databases.


Can't perform this operation; features in this version are not available in databases with older formats. (Error 3301)

The database was stored in an earlier version of the Microsoft Jet database engine that doesn't support this feature. Either the database needs to be converted to Microsoft Jet version 2.0 or 3.0 format or this particular operation needs to be revised to avoid using the unsupported feature.


Can't change a rule while the rules for this table are in use. (Error 3302)

A record in this table has been changed by another user, or has been changed by you in a separate session of your application, and is currently locked. You can't modify the rules in a table while a record in that table is locked.

If you have locked the record in a separate session, save the record, and then make your changes. If another user has locked the record, wait a little while, and then save your rule modifications.


Can't delete this field. It's part of one or more relationships. (Error 3303)

You're trying to delete a field for which relationships have been defined in the database. To delete the field, you must first delete its relationships.


You must enter a personal identifier (PID) consisting of at least 4 and no more than 20 characters and digits. (Error 3304)

A personal identifier (PID) must be at least 4 characters and no more than 20 characters long.


Invalid connection string in pass-through query. (Error 3305)

The connection string for a pass-through query should begin with "ODBC;".


You've written a subquery that can return more than one field without using the EXISTS reserved word in the main query's FROM clause. Revise the SELECT statement of the subquery to request only one field. (Error 3306)


The number of columns in the two selected tables or queries of a union query don't match. (Error 3307)

The two tables or queries joined by the UNION operation must generate the same number of columns. Remove columns from the SELECT statement that has too many columns or include more columns in the SELECT statement that has too few.

Note   You can include constants instead of columns in the SELECT statement that has too few columns. For example, the following union query generates three columns from the first SELECT statement but one column and two constants in the second SELECT statement. The query returns all countries in the Employees and Regions tables. From the Employees table, the query also returns the first and last name of an employee. If the country value is from the Regions table, however, the query returns Null in the First Name and Last Name columns.

SELECT Country, FirstName, LastName FROM Employees

UNION SELECT Country, NULL, NULL FROM Regions;


Invalid TOP argument in select query. (Error 3308)

An invalid parameter appeared in the TOP clause of a SELECT statement. The value placed after the TOP reserved word must be a positive integer. If the PERCENT reserved word is also used, the integer can't be greater than 100.


Property setting can't be larger than 2K. (Error 3309)

You are trying to set a property value of an object to a size greater than the largest permissible size of 2K. Shorten the length of the property value.


This property isn't supported for external data sources or for databases created with a previous version of Microsoft Jet. (Error 3310)

You attempted to set or check a property that isn't available for this object in a database stored in a Microsoft Jet database version 1.x, 2.x, or in an external data source. Search for the object in Help, and then display the Summary topic for the object to see a list of its valid properties.


Property specified already exists. (Error 3311)

You tried to append a new Property object to a collection that contains a property of the same name. Check to see whether you've misspelled the new Property object's Name property, or refer to the Help topic for the existing property of the same name to see whether you need to create a new Property object.


Validation rules and default values can't be placed on system or linked tables. (Error 3312)

You're trying to set the DefaultValue, ValidationRule, ValidationText, or Required property on a table, field, or other object that is prohibited by your application. For example, you're setting a property on a system object.


Can't place this validation expression on this field. (Error 3313)

You're trying to set validation properties on a field (such as an AutoNumber or OLE Object field) that doesn't allow this type of property. Use a different field to validate data or, if you have not added data to the table, redefine the data type for the field.


The field <name> can't contain a Null value because the Required property for this field is set to True. Enter a value in this field. (Error 3314)

The Required property for this field is set to True, prohibiting the entry of a Null in the field. Enter a value in the field.


Field <name> can't be a zero-length string. (Error 3315)

The AllowZeroLength property for this field is set to False, prohibiting the entry of a zero-length string in the field. Enter a different value in the field.


<Table-level validation text>. (Error 3316)

A table-level validation rule was violated.


One or more values are prohibited by the validation rule <rule> set for <name>. Enter a value that the expression for this field can accept. (Error 3317)

The ValidationRule property for this field contains an expression that limits the values that can be entered in the field. You must enter a value that isn't prohibited by the expression.


Values specified in a TOP clause are not allowed in delete queries or reports. (Error 3318)

Top values, that is, those specified in a TOP clause of a SELECT statement, aren't allowed in delete queries or in reports.


Syntax error in union query. (Error 3319)

There is a syntax error in an SQL string of the union query.

Possible causes:

•	A reserved word or argument name is misspelled.

•	A reserved word or argument is missing.

•	Punctuation is incorrect.


<Error> in table-level validation expression. (Error 3320)

An error occurred in a table-level validation rule expression or its default value expression. This could be a syntax error or some other kind of error.


No database specified in connection string or IN clause. (Error 3321)

The Microsoft Jet database engine is unable to connect to an external ISAM database because you haven't specified the name of the database to connect to. When connecting to an external source of data, you must specify a database name.

Possible causes:

•	The connection string in the FROM clause of the SELECT statement is missing the parameter, DATABASE=.

•	The IN clause of the SELECT statement includes a database type argument (indicating to select the data from an external database) but it's missing a database name argument.


Crosstab query contains one or more invalid fixed column headings. (Error 3322)

The list of entries for a fixed column heading of a crosstab query (the PIVOT clause in a TRANSFORM statement) isn't valid.

Possible causes:

•	There are no entries in the list. There must be at least one value in the parentheses following the IN reserved word in the PIVOT clause.

•	A blank entry appears in the list. Two commas in a row (,,) create a blank entry.

•	The list contains a field name of more than 64 characters.

Correct the PIVOT clause and execute the query again.


The query cannot be used as a row source. (Error 3323)

Possible causes:

•	The query being used as a record source is an action query or a data-definition query.


The query is a DDL query and cannot be used as a row source. (Error 3324)

You tried to run an action query or data-definition query without using the Execute method.


Pass-through query with ReturnsRecords property set to True did not return any records. (Error 3325)

A pass-through query didn't return any records even though the ReturnsRecords property is set to True. If a pass-through query doesn't return records, set the ReturnsRecords property to False.


This Recordset is not updatable. (Error 3326)

You attempted to edit data in a field that is bound to a snapshot-type Recordset object. Snapshot fields in a Microsoft Jet database can't be edited.


Can be present only in version 1.0 format. (Error 3334)

You are attempting to use a feature that is no longer supported in the current version of the application.


Btrieve: Invalid IndexDDF option in initialization setting. (Error 3336)

The setting for the IndexDDF value in the Btrieve key of the Windows Registry isn't valid. The IndexDDF value determines the manner in which the Btrieve external ISAM database is to handle the INDEX.ddf file, which is updated whenever indexes are created or deleted.

Valid settings are:

•	Require — INDEX.ddf file is required in the database directory, in addition to FILE.ddf and FIELD.ddf.

•	Maintain — Updates the INDEX.ddf file if it exists, but doesn't generate an error if it doesn't.

•	Ignore — Makes no attempt to update the INDEX.ddf file, regardless of whether or not it exists.


Invalid DataCodePage option in initialization setting. (Error 3337)

The DataCodePage setting for the external data source you are attempting to use isn't valid. This setting is in the corresponding \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engine\<external data source ISAM> in the Windows Registry.

Valid settings are:

•	OEM — Data is stored as OEM data; OemToAnsi and AnsiToOem conversions are done.

•	ANSI — Data is stored as ANSI data; OemToAnsi and AnsiToOem conversions aren't done.


Btrieve: Xtrieve options aren't correct in initialization setting. (Error 3338)

One or more of the XTRPATH, XTRENV, and XTRPINDEX settings in the Windows Registry is invalid.

Possible causes and solutions:

•	XTRPATH is the directory search path for locating data files. The format for this entry is:

XTRPATH=dir1;dir2;dir2

where dir1, dir2, and dir3 are full directory paths (for example, XTRPATH=C:\DATA;D:\FILES;E:\DATA).

•	XTRENV is the directory and filename for the Xtrieve environment file (for example, XTRENV=C:\XTRV\XTRIEVE.env).

•	XTRPINDX is a pointer to the directory in which to create new Xtrieve tables, expressed as a numeric value corresponding to a directory in XTRPATH, with the first directory having an XTRPINDX of 1, the second having an XTRPINDX of 2, and so on. In the XTRPATH shown previously , an XTRPINDX value of 2 indicates create new Xtrieve tables in the directory D:\FILES.


Btrieve: Invalid IndexDeleteRenumber option in initialization setting. (Error 3339)

The setting for the IndexDeleteRenumber entry in the Btrieve key of the Windows Registry isn't valid. The IndexDeleteRenumber entry determines whether remaining indexes are renumbered if one is deleted.

Valid settings are:

•	On — Renumbers.

•	Off — Doesn't renumber.

On is consistent with Btrieve version 5.1x behavior. Off is consistent with Btrieve version 6.0 behavior.


Query <name> is corrupt. (Error 3340)

You've referenced an undefined query name. Check the queries listed in the QueryDefs collection to make sure you referenced a valid query name.


The current field must match the join key <name> in the table that serves as the 'one' side of one-to-many relationship. Enter a record in the 'one' side table with the desired key value, and then make the entry with the desired join key in the 'many-only' table. (Error 3341)

You've tried to enter a value into the join field in the many-only table of an outer join with no corresponding value in the join field of the "one" side table. First enter a record in the "one" side table with the desired key value. Then make the entry with the desired join field in the "many-only" table.


Invalid Memo or OLE Object in subquery <name>. (Error 3342)

A subquery can't return a Memo or OLE Object, and it can't be compared to a Memo or OLE Object in an expression.


The database engine does not recognize either the field <name> in a validation expression, or the default value in the table <name>. (Error 3344)

Your expression refers to a field incorrectly, or to a field that doesn't exist. Check to make sure the field name is valid and spelled correctly.


Unknown or invalid field reference <name>. (Error 3345)

Your expression refers to a field incorrectly or to a field that doesn't exist. Check to make sure the field name is correct.


Number of query values and destination fields aren't the same. (Error 3346)

The INSERT INTO (append) query either doesn't have enough destination fields or it has more fields in the VALUES or SELECT list than there are fields in the destination table. Select a matching number of fields.


Numeric field overflow. (Error 3349)

The data in a Btrieve field is too large to represent in your application.


Object is invalid for operation. (Error 3350)

You used the RefreshLink method on an object other than a linked table. An object ceases to exist when it is destroyed and when its associated DAO object is closed or is no longer defined in the current scope.


The ORDER BY expression <expression> includes fields that aren't selected by the query. Only those fields requested in the first query can be included in an ORDER BY expression. (Error 3351)

In a union query, you've included fields in an ORDER BY expression that aren't specified by the query. Only those fields requested in the first query can be included in an ORDER BY expression.


No destination field name in INSERT INTO statement <statement>. (Error 3352)

The destination field name or names can't be determined from the expression in the SELECT clause of the INSERT INTO statement.


Btrieve: Can't find file Field.ddf. (Error 3353)

The Btrieve driver can't find the Field.ddf file pointed to by the File.ddf file.

Possible solutions:

•	If the Field.ddf file exists, fix the reference to it in the File.ddf file using either Novell Xtrieve or another .ddf file builder.

•	If the Field.ddf file doesn't exist, create it using either Novell Xtrieve or another .ddf file builder.


At most one record can be returned by this subquery. (Error 3354)

A subquery of this kind can't return more than one record. Revise the SELECT statement of the subquery to request only one record.


Syntax error in default value. (Error 3355)

Possible causes:

•	An unknown function name was included in the default value expression in a table-level validation rule.

•	A default value expression in a table-level validation rule is syntactically incorrect.


You attempted to open a database that is already opened exclusively by user <name> on machine <name>. Try again when the database is available. (Error 3356)

Possible causes:

•	You attempted to open a database that is already opened exclusively by the specified user <name>. You cannot open the database until the other user closes it.

•	You attempted to open exclusively a database that is already open in shared (non-exclusive) mode by the specified user <name>. You can open the database only in shared mode until the other user closes it.


Can't open the Microsoft Jet engine workgroup information file. (Error 3358)

You attempted to perform a security-related task, but the workgroup information file (typically System.mdw) required for the task can't be found.


Pass-through query must contain at least one character. (Error 3359)

The SQL string of a pass-through query must contain at least one character.


Query is too complex. (Error 3360)

The query is too complex. Reduce the number of fields in the SELECT clause or the number of subqueries or tables in the join.


Unions not allowed in a subquery. (Error 3361)

You can't use a UNION operation in a subquery expression. To use a union query in a subquery, first create the union query and save it as a named query. Then include the name of the saved query in your subquery expression.


Single-row update/delete affected more than one row of a linked table. Unique index contains duplicate values. (Error 3362)

Your update or delete query affected more than one record in the linked SQL table. An update and delete query can affect only one record at a time.


Can't use Memo or OLE Object field <name> in the SELECT clause of a union query. (Error 3364)

A field you specified in the SELECT part of a union query in the SQL statement for the query has a field data type of Memo or OLE object. You can't specify a field of either of these types.


Can't set this property for remote objects. (Error 3365)

This property isn't available for objects associated with ODBC databases.


Can't append a relation with no fields defined. (Error 3366)

You are trying to append a Relation object to a Relations collection, but the Relation object has no fields.

To correctly append a Relation

1	Use the CreateRelation method to create the Relation object.

2	Set the Table, ForeignTable, and Attributes properties of the Relation object, if you didn't specify them as arguments to the CreateRelation method.

3	Use the CreateField method to create a new Field object for each field in the primary and foreign keys of the relationship.

4	Set the Name (if you didn't specify it as an argument to the CreateField method) and ForeignName properties of the Field object or objects to the corresponding Name property settings of the primary key and the foreign key Field objects of each field in the relationship.

5	Use the Append method to save the Field object or objects in the Fields collection of the Relation object.

6	Use the Append method to save the Relation object in the Relations collection of the database.


Can't append. An object with that name already exists in the collection. (Error 3367)

You tried to append an object to a collection that already contains an object of the same name. Use the Refresh method on the collection and check to see whether the object you want to append already exists, or try changing the object's Name property setting.


Relationship must be on the same number of fields with the same data types. (Error 3368)

The CONSTRAINT clause you're using to create a relationship includes a different number of fields for each table or includes fields with different data types. Check the number of fields in the CONSTRAINT clause, check the data types of fields to make sure they match, and try again.


Can't modify the design of table <name>. It's in a read-only database. (Error 3370)

You can't modify tables in a read-only database.


Can't find table or constraint. (Error 3371)

The table or relationship you specified doesn't exist. Specify a valid table or constraint name.


No such index <name> on table <name>. (Error 3372)

The specified index doesn't exist in the specified table. Check your code for a misspelling or other error, or verify the Indexes collection contains the specified index.


Can't create relationship. Referenced table <name> doesn't have a primary key. (Error 3373)

The table you've referenced in the CONSTRAINT clause doesn't have a primary key. To create the relationship, you must either create a primary key in the referenced table, or specifically reference one or more uniquely indexed fields to use in the relationship.


The specified fields are not uniquely indexed in table <name>. (Error 3374)

The specified fields in the referenced table of a CONSTRAINT clause aren't uniquely indexed.


Table <name> already has an index named <name>. (Error 3375)

You're trying to create an index that already exists.


Table <name> doesn't exist. (Error 3376)

The table you specified doesn't exist. Check to see if the name you specified exists in the TableDefs collection.


No such relationship <name> on table <name>. (Error 3377)

The relationship you specified doesn't exist in this database. Check to see if the name you specified exists in the Relations collection.


There is already a relationship named <name> in the current database. (Error 3378)

You must specify a unique name for each relationship you add to a database by using data-definition queries. Check to see if the name you specified exists in the Relations collection.


Can't create relationships to enforce referential integrity. Existing data in table <name> violates referential integrity rules in table <name>. (Error 3379)

You're trying to create a relationship using the CONSTRAINT clause of the ALTER TABLE statement, but existing data in the two tables violates referential integrity constraints. For example, there might be records relating to an employee in the related table but no corresponding record for the employee in the primary table.

To create the relationship, you must edit the data so that primary records exist for all related records.


Field <name> already exists in table <name>. (Error 3380)

You have entered the same field name twice. Rewrite your code, giving each field a unique name. You should also check to see if the field name exists in the Fields collection.


There is no field named <name> in table <name>. (Error 3381)

The specified table doesn't contain the specified field. Check the spelling of the field name. You should also check to see if the field name exists in the Fields collection.


Size of field <name> is too long. (Error 3382)

Text fields in Microsoft FoxPro tables can be no more than 254 characters, and in Microsoft Jet tables, no more than 255 characters. Redefine the size of the field.


Can't delete field <name>. It's part of one or more relationships. (Error 3383)

You're trying to delete a field for which relationships have been defined in the database. To delete the field, you must first delete its relationships.


Can't delete a built-in property. (Error 3384)

You are trying to delete a Property object defined by the Microsoft Jet database engine.

You can delete only user-defined (including application-defined) properties for which you have permission to modify the design, or ones for which this permission isn't required.


User-defined properties don't support a Null value. (Error 3385)

User-defined Property objects can't be set to Null. Instead, use the Delete method on the property to remove it from its collection.


Property <name> must be set before using this method. (Error 3386)

You attempted to append a new Property object to a collection without first setting all of the new object's properties: Value, Type, and Name.


Unknown function <name> in validation expression or default value on <name>. (Error 3388)

The function you are referencing is either unknown (because the name is invalid or misspelled) or is a type of function not allowed by the ValidationRule or DefaultValue property. Among the types of functions not allowed are user-defined, SQL aggregate functions.


Query support unavailable. (Error 3389)

You attempted to establish referential integrity on a Relation object of a QueryDef object, which isn't supported.

Change the Attributes property setting of the Relation object to dbRelationDontEnforce.


Account name already exists. (Error 3390)

This is a security problem. You tried to establish a user account using a name that already exists. Check the Users collection to see if the user name already exists, or try again using a different user name.


Can't perform join, group, sort, or indexed restriction. A value being searched or sorted on is too long. (Error 3393)

The maximum combined length of fields used to join, group, or sort is 255 bytes. Reduce the number of fields in your join, group, or sort, or use shorter data types and field sizes for the fields.


Can't save property; property is a schema property. (Error 3394)

You tried to set or change a schema property. When you create a new schema property, specify True as the fourth argument to the CreateProperty method in order to set or delete this property.


Can't perform cascading operation. Since related records exist in table <name>, referential integrity rules would be violated. (Error 3396)

The cascade operation you are attempting violates referential integrity rules with the indicated table. Check the values you are attempting to update or delete, and fix them so they comply with the referential integrity rules.


Can't perform cascading operation. There must be a related record in table <name>. (Error 3397)

The cascade operation you are attempting violates a referential integrity rule that requires a related record in the indicated table. Check the values you are attempting to update or delete, and fix them so they comply with the referential integrity rule.


Can't perform cascading operation. It would result in a null key in table <name>. (Error 3398)

The cascade operation you are attempting would result in a Null value in a primary key field in the indicated table, which has been set up not to allow Null values. Check the values you are attempting to update and fix them so they don't result in Null values.


Can't perform cascading operation. It would result in a duplicate key in table <name>. (Error 3399)

The cascade operation you are attempting would result in a duplicate key in the indicated table, which is set up to not allow duplicate primary keys. Check the values you are attempting to update and fix them so they don't result in duplicate keys.


Can't perform cascading operation. It would result in two updates to field <name> in table <name>. (Error 3400)

The cascade operation you are attempting can't be completed because it would result in two separate updates to the indicated field. Check the values you are attempting to update, and fix them so that either:

•	The field is updated only one time.

•	If the field is updated more than once, the result of each update to the field is the same.


Can't perform cascading operation. It would cause field <name> to become Null, which is not allowed. (Error 3401)

The cascade operation you are attempting would result in a Null value in the indicated field, which has been set up to not allow Null values. Check the values you are attempting to update and fix them so they don't result in Null values in this field.


Can't perform cascading operation. It would cause field <name> to become a zero-length string, which is not allowed. (Error 3402)

The cascade operation you are attempting would result in a zero-length string in the indicated field, which is set up to not allow zero-length strings. Check the values you are attempting to update and fix them so they don't result in zero-length strings in this field.


Can't perform cascading operation: <validation text>. (Error 3403)

The cascade operation you are attempting would result in invalid data. Check the values you are attempting to update and fix them so they comply with the validation rules.


Can't perform cascading operation. The value entered is prohibited by the validation rule <rule> set for <name>. (Error 3404)

The cascade operation you are attempting would result in an invalid value in the indicated field, as established by the field's validation rule. Check the values you are attempting to update and fix them so they comply with the validation rule.


Error <error text> in validation rule. (Error 3405)

The expression cannot be evaluated correctly for the reason given in the alert. For example, if the error text is "Type Mismatch," the property setting doesn't match the data type defined for the field.


The expression you're trying to use for the DefaultValue property is invalid because <error text>. Use a valid expression to set this property. (Error 3406)

The expression you're trying to use for the DefaultValue property is invalid. Set the property to a valid expression.


The server's MSysConf table exists, but is in an incorrect format. Contact your system administrator. (Error 3407)

The MSysConf table created on the server to help control communications between the Microsoft Jet database engine and the linked ODBC data source requires a very specific format.


Invalid field name <name> in definition of index or relationship. (Error 3409)

Possible causes:

•	The field name you've specified might be misspelled. Check the spelling of the field name.

•	You tried to update an AutoNumber field, but AutoNumber fields can't be updated.


Invalid entry. Can't perform cascading operation in table <name> because the value entered is too large for field <name>. (Error 3411)

You're trying to save a value to a primary key field that's included in a relationship.

In Microsoft Access, the Cascade Update Related Fields option is selected for the relationship; or, in DAO code, the dbRelationUpdateCascade option is specified for the Relation object's Attributes property. Setting either one of these options will cause your application to attempt to update the matching field in the related table.

To save your changes to this field, the text you enter must be no longer than the field size of the related field that your application is trying to update for you. In this case, the related field has a shorter field size than the field you're updating. To avoid this problem in the future, set the Size property for both of the matching fields to the same value.


Can't perform cascading update on the table because it is currently in use by another user. (Error 3412)

You're trying to save a value into a primary key field that's included in a relationship.

In Microsoft Access, the Cascade Update Related Fields option is selected for the relationship, or in DAO code, the dbRelationUpdateCascade option is specified for the Relation object's Attributes property. Your application is attempting to update the matching field in the related table.

The matching field can't be updated because of a locking conflict with another user. To save the record, you must wait until the related table is no longer in use.


Can't perform cascading operation on table <name> because it is currently in use. (Error 3414)

You're trying to save a value to a primary key field that's included in a relationship.

In Microsoft Access, the Cascade Update Related Fields option is selected for the relationship, or in DAO code, the dbRelationUpdateCascade option is specified for the Relation object's Attributes property. Therefore, your application is attempting to update the matching field in the related table.

The matching field can't be updated because you have it open or locked on your computer. To save the record, you must first close the related table.


Zero-length string is valid only in a Text or Memo field. (Error 3415)

You're trying to enter a zero-length string in a field that has a data type other than Text or Memo. You may be able to enter a Null value instead.


An action query cannot be used as a row source. (Error 3417)

Possible cause:

•	The query being used as a record source is an action query or a data-definition query.


Can't open <tablename>. Another user has the table open using a different network control file or locking style. (Error 3418)

The Microsoft Jet database engine can't open an external Paradox table because of inconsistencies between your initialization settings and those of another user who currently has the table open. The ParadoxNetPath and the ParadoxNetStyle settings in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Paradox key of the Windows Registry must be consistent for all users sharing a database. Make sure your initialization settings match those of all other users sharing the database, and then try opening the table again.


Can't open this Paradox 4.x or 5.x table because ParadoxNetStyle is set to 3.x in the Windows Registry. (Error 3419)

The Microsoft Jet database engine was unable to open an external Paradox table because of inconsistencies between the version of the table and your ParadoxNetStyle setting in the Windows Registry.

To correct the problem

1	Exit your application.

2	Start the Registry Editor, navigate to the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Paradox key, and select the ParadoxNetStyle value.

3	On the Edit menu, click Modify.

4	Specify the value 4.x in the Value data box.

The ParadoxNetStyle setting must be consistent for all users sharing a database.

5	Restart your application.

6	Try opening the table again.


Object is invalid or no longer set. (Error 3420)

You are attempting to reference an object that is no longer valid or has not been set.

Possible causes:

•	The object has been closed.

•	The object has been orphaned (the parent object has been closed or deleted).

•	The object is out of scope.

•	The object library isn't registered in the Windows Registry.

•	You are trying to reference a method or property of the collection, but you haven't assigned it to a variable first. For example, to reference the Name property, use the following:

Dim dbsPublish As Database

Set dbsPublish = OpenDatabase("BIBLIO.mdb")

dbname = dbsPublish.Name


Data type conversion error. (Error 3421)

The Microsoft Jet database engine was unable to convert data into the type required by a method or property. This problem typically occurs if you use an argument of one type when a method or property expects another type.


Can't modify table structure. Another user has the table open. (Error 3422)

The Microsoft Jet database engine was unable to modify the structure of a table because another user currently has the table open. Wait until the table is closed, and then try making your changes again.


You cannot use ODBC to import from, export to, or link an external Microsoft Jet or ISAM database table to your database. (Error 3423)

You are attempting to link, import data from, or export data to either an external Microsoft Jet table or an external ISAM database table (for example, dBASE, FoxPro, Paradox, or Btrieve), but you've selected <SQL Database> as the data source. You must select the appropriate data source for the data you're attempting to link.


A problem occurred in your database. Correct the problem by repairing and compacting the database. (Error 3428)

The database you are attempting to use has an unspecified problem and, as a result, it is marked as corrupt.

To correct the problem

1	Close the database.

2	Repair the database with the RepairDatabase method. In Microsoft Access, you can also do this by going to the Tools menu, pointing to pointing to Database Utilities, and then clicking Repair Database.

3	Compact the database with the CompactDatabase method. In Microsoft Access, you can also do this by going to the Tools menu, pointing to Database Utilities, and then clicking Compact Database.

Important   All steps are required.


Incompatible version of an installable ISAM. (Error 3429)

You attempted to use an older version of an installable ISAM with the current version of the Microsoft Jet database engine. Run Setup again to install the correct version of the installable ISAM.


While loading the Microsoft Excel installable ISAM, OLE was unable to initialize. (Error 3430)

OLE Automation was unable to initialize while loading the Microsoft Excel installable ISAM. Try reinstalling the OLE DLL files.


This is not a Microsoft Excel 5.0 file. (Error 3431)

You attempted to read a file as a Microsoft Excel version 5.0 file, but the file isn't in this format.


Error opening a Microsoft Excel 5.0 file. (Error 3432)

An OLE error occurred while opening a Microsoft Excel version 5.0 file.


Invalid setting in Excel key of the Engines section of the Windows Registry. (Error 3433)

One of the settings in the \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Excel key of the Windows Registry isn't valid. Edit the Windows Registry to be sure all the parameters are valid.


Can't expand named range. (Error 3434)

Cells with values were encountered while attempting to add rows to a Microsoft Excel version 5.0 named range. These cells can't be overwritten by an append operation.


Cannot delete spreadsheet cells. (Error 3435)

Data in the specified spreadsheet range of cells can't be deleted. These cells may contain formulas, or they may be protected cells.


Failure creating file. (Error 3436)

An error occurred while attempting to create a Microsoft Excel or text file or Lotus installable ISAM.

Possible causes:

•	Insufficient disk space

•	Network failure


Spreadsheet is full. (Error 3437)

You tried to add new records to a Lotus 1-2-3 or Microsoft Excel version 3.0 or version 4.0 file, but the file is full. Files of these types can hold a maximum of 16,384 records.


The data being exported does not match the format described in the Schema.ini file. (Error 3438)

Make sure the data being exported matches the format described in the Schema.ini file.


You attempted to link or import a Microsoft Word mail merge file. Although you can export such files, you cannot link or import them. (Error 3439)

You attempted to link or import a Microsoft Word mail merge file. Although you can export such files, you can't link or import them.


An attempt was made to import or link an empty text file. To import or link a text file, the file must contain data. (Error 3440)

You attempted to import or link an empty text file. To import or link a text file, the file must contain data.


In the text file specification <name>, the <name> option is invalid. (Error 3442)

One of the options in the text file specification for the Text ISAM is invalid. The specification can be set in a number of ways:

•	From Microsoft Access, these values are set in the Link Text wizard (which you can use by pointing to Get External Data on the File menu, and then clicking Link Tables). You can also see them in the system tables MSysIMEXSpecs and MSysIMEXColumns.

•	From other Microsoft Jet host applications, these values are stored in the Schema.ini file.


The fixed-width specification <name> contains no column widths. (Error 3443)

The fixed-width parameter specified in the text file specification for the Text ISAM is invalid does not specify a column width. The specification can be set in a number of ways:

•	From Microsoft Access, these values are set in the Link Text Wizard (which you can use by pointing to Get External Data on the File menu, and then clicking Link Tables).

•	From other Microsoft Jet host applications, these values are stored in the Schema.ini file.


In the fixed width specification <name>, column <column> does not specify a width. (Error 3444)

No column width parameter is specified in the text file specification for the Text ISAM is invalid. The specification can be set in a number of ways:

•	From Microsoft Access, these values are set in the Link Text Wizard (which you can use by pointing to Get External Data on the File menu, and then clicking Link Tables).

•	From other Microsoft Jet host applications, these values are stored in the Schema.ini file.


This query is not a properly formed data-definition query. (Error 3357)

This query is not a properly formed data-definition query.


<reserved error alert> (Error 3416)

This error was generated by an application released after this version of the Microsoft Jet database engine. Contact Microsoft Product Support Services.


Can't create database because the locale is invalid. (Error 3424)

An invalid locale parameter was specified. Make sure you are using a valid Data Access Objects (DAO) constant to specify the locale parameter.


Text file specification field separator matches decimal separator or text delimiter. (Error 3441)

Two or more of the following delimiters settings used by the Text ISAM are the same:

TxtDelimiter

NumberDecimalSymbol

CurrencyDecimalSymbol

Format


Incorrect version of the DLL file <name> was found. (Error 3445)

For Microsoft Jet databases, the installed Jet DLL (msajt200.dll for 16-bit versions, or msjt2032 for 32-bit versions) must be version 2.5 or later.

For ODBCDirect databases, the installed Remote Data Objects (RDO) DLL (msrdo32.dll) must be version 1.0 or later.

Try reinstalling the application that returned the error.


Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) is missing. Try reinstalling the application that returned the error. (Error 3446)

The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) could not be found. Try reinstalling the application that returned the error.


The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) failed to initialize when called. Try reinstalling the application that returned the error. (Error 3447)

The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) did not initialize when it was called. Try reinstalling the application that returned the error.


A call to an OLE system function was not successful. Try reinstalling the application that returned the error. (Error 3448)

An OLE Automation function called failed. Try reinstalling the application that returned the error.


No country code found in the connection string. (Error 3449)

No country code was found in the connection string.


Data type mismatch in criteria expression. (Error 3464)

The criteria expression in a Find method is attempting to compare a field with a value whose data type does not match the field’s data type.


Record length is too long for an indexed Paradox table. (Error 3608)

An indexed Paradox table has a maximum record length of 1350 bytes. Try reducing the size of some Text or Memo fields.


No unique index found for the referenced field of the primary table. (Error 3609)

When you create a relationship between tables, the referenced field in the primary table must have a unique index. See the Index object and Primary property topics for more details on how to do this.


Same table <table> referenced as both the source and destination in a make-table query. (Error 3610)

One of the source tables in a SELECT INTO statement is also named as the destination table. Either remove the table from the source tables or rename the destination table.


Can't execute data definition statements on linked data sources. (Error 3611)
Can’t execute data definition statements on linked data sources. (Error 3611)

The Microsoft Jet database engine cannot create an index on a linked ISAM table, or on an ODBC table that already has a unique index.


Multi-level GROUP BY clause is not allowed in a subquery. (Error 3612)

An SQL subquery cannot list more than one field in a GROUP BY clause.


Can't create a relationship on linked ODBC tables. (Error 3613)
Can’t create a relationship on linked ODBC tables. (Error 3613)

The Microsoft Jet database engine cannot create a relationship on linked tables in ODBC data source tables.


GUID not allowed in Find method criteria expression. (Error 3614)

The criteria expression in a Find method cannot reference a GUID.


Type mismatch in JOIN expression. (Error 3615)

A JOIN expression is attempting to join two tables on fields of incompatible data types. For example, you will get this error if you attempt to join a Memo field with a Text field.


Updating data in a linked table is not supported by this ISAM. (Error 3616)

The installable ISAM you are using does not allow updates to records in external tables. You can only add new records.


Deleting data in a linked table is not supported by this ISAM. (Error 3617)

The installable ISAM you are using does not allow you to delete records in external tables. You can only add new records.


You can't make changes to the design of the database at this replica. (Error 3452)

Changes to the design of a replicated database can be made only at the Design Master. The replica you are attempting to change is not the Design Master for the replica set. Locate the Design Master and make your changes there.


You can't establish or maintain an enforced relationship between a replicated table and a local table. (Error 3453)

You are attempting to establish or maintain an enforced relationship between a replicated table and a non-replicated table. Replication does not allow an enforced relationship between:

•	A replicated table and a local table.

•	Two local tables that you are making replicable.

•	Two tables with different KeepLocal property settings.

Delete the relationship between the two tables before proceeding.


Can't make the database replicable. (Error 3455)

The Microsoft Jet database engine was in the process of making the database replicable. The operation failed because there were insufficient resources. Make sure the total number of fields after replication does not exceed 255 in a single table and the total number of bytes in a record does not exceed 2048.


The object named <name> in the <name> collection cannot be made replicable. (Error 3456)

The Microsoft Jet database engine was in the process of making the object replicable. The operation failed because there were insufficient resources to manipulate the object. If the object is a table, make sure the total number of fields after replication does not exceed 255 and the total number of bytes in a record does not exceed 2048. If the number of fields or characters is over the limit, decrease the size of the record.


You can't set the KeepLocal property for an object that is already replicated. (Error 3457)

The KeepLocal property cannot be set on a replicated object. Setting a local object's KeepLocal property after the database has been replicated has no effect on the object. If you want to keep an object from being replicated to the other replicas in the set, set the object's Replicable property to "F".


The KeepLocal property cannot be set on a database; it can be set only on the objects in a database. (Error 3458)

The KeepLocal property is set to "T" for objects in a database that you do not want replicated. You cannot set this property for the entire database.


After a database has been replicated, you cannot remove the replication features from the database. (Error 3459)

You can't remove the replication features from a database that has been replicated, either by setting its Replicable property to "T" or by converting it with the Windows Briefcase, Microsoft Access, or the Replication Manager. Using DAO to set the database's Replicable property to "F" or any other value has no effect on the replicated database. If you need to use a copy of the database that does not have the properties, fields, tables, and other characteristics associated with replication, open the backup copy of the database made before the database was first converted.


The operation you attempted conflicts with an existing operation involving this member of the replica set. (Error 3460)

Another user or application is already performing the same operation on this member of the replica set. Retry your action later.


The replication property you are attempting to set or delete is read-only and can't be changed. (Error 3461)

Many properties related to replication are for internal use only or are available to the developer on a read-only basis. Review your program code to make sure you are reading rather than changing the property.


Failure to load a DLL. (Error 3462)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Can't find the .dll <name>. (Error 3463)

Make sure that the specified dynamic-link library is in your path or reinstall Replication Manager (or your application).


The disk drive you are attempting to access is unreadable. (Error 3465)

If you are attempting to access a floppy disk, make sure the door to the disk drive is closed. If you are attempting to access a hard disk, the disk might have a corrupted sector.


Access was denied while accessing dropbox folder <name>. (Error 3468)

Check your permissions for the dropbox folder.


The disk for dropbox folder <name> is full. (Error 3469)

There is not enough space on the dropbox folder's disk drive to complete the operation. Delete unneeded files from the disk to create sufficient space for the operation.


Disk failure accessing dropbox folder <name>. (Error 3470)

The disk might have a corrupted sector.


Failure to write to the Synchronizer log file. (Error 3471)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Disk full for path <name>. (Error 3472)

Remove files from the disk drive to free up space.


Disk failure while accessing log file <name>. (Error 3473)

The disk drive for the log file may have a bad sector.

To select a different disk drive for the log file, open the Replication Manager, and on the Tools menu, click Configure Microsoft Replication Manager. Or run the Setup program for the application using replication.


Can't open the log file <name> for writing. (Error 3474)

Make sure you have permission to write to the log file.


Sharing violation while attempting to open log file <name> in Deny Write mode. (Error 3475)

Close the log file in all other applications.


Invalid dropbox path <name>. (Error 3476)

Make sure the dropbox path is correct.

Open the Replication Manager, go to the Tools menu, and then click Configure Microsoft Replication Manager. Or run the Setup program for the application using replication.


Dropbox address <name> is syntactically invalid. (Error 3477)

Reset your dropbox folder. Open the Replication Manager, go to the Tools menu, and then click Configure Microsoft Replication Manager. Or run the Setup program for the application using replication.


The replica is not a partial replica. (Error 3478)

You are attempting to get information about the filter or some other aspect of a partial replica. However, the replica you are querying is not a partial replica. Use the Replication Manager to view the replica’s property sheet and confirm that the replica is not a partial replica.


Can't designate a partial replica as the Design Master for the replica set. (Error 3479)

Select a different replica to become the Design Master.


The relationship <name> in the partial filter expression is invalid. (Error 3480)

Specify a valid relationship.


The table name <name> in the partial filter expression is invalid. (Error 3481)

Make sure you are using the correct table name in the expression.


The filter expression for the partial replica is invalid. (Error 3482)

The ReplicaFilter property was set to an invalid string.


The password supplied for the dropbox folder <name> is invalid. (Error 3483)

To specify the password, start the Replication Manager. On the Tools menu , click Configure Microsoft Replication Manager, and re-enter the password for the dropbox folder.


The password used by the Synchronizer to write to a destination dropbox folder is invalid. (Error 3484)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The object can't be replicated because the database is not replicated. (Error 3485)

You can't replicate an object in a database unless you first replicate the database that contains it. You can replicate the database by:

•	Dragging it into the Windows Briefcase.

•	Using DAO programming to set the Replicable property to "T" or the ReplicableBool property to True.

•	Using Microsoft Access.

•	Using the Replication Manager.

All objects in the database are replicated when the database is replicated, unless the KeepLocal property has been set on an object.


You can't add a second Replication ID AutoNumber field to a table. (Error 3486)

The table you are attempting to change already has one field that uses the Replication ID AutoNumber (or GUID) data type. If you are attempting to create a second Replication ID field to serve as a foreign key, use the Number data type instead of the AutoNumber data type.


The database you are attempting to replicate can't be converted. (Error 3487)

Only databases created with version 3.0 or later of the Microsoft Jet database engine can be replicated. Although you can open the database by using an installable ISAM, you cannot convert it to a replicable form. If the database was created by using an earlier version of Microsoft Jet, convert the format to the newer version by going to the Microsoft Access Tools menu, pointing to Database Utilities, and then clicking Convert Database. If the database is in another format, export the data to a new Microsoft Jet database and retry.


The value specified is not a ReplicaID for any member in the replica set. (Error 3488)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The object specified can't be replicated because it is missing a necessary resource. (Error 3489)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Can't create a new replica because the <name> object in <name> container could not be replicated. (Error 3490)

The Microsoft Jet database engine was in the process of creating a replica. The operation failed when it attempted to act on the object and container identified in the error message.


The database must be opened in exclusive mode before it can be replicated. (Error 3491)

You attempted to replicate a database after opening the database in shared mode. Close the database and reopen it in exclusive mode, and then replicate it.


The synchronization failed because a design change could not be applied to one of the replicas. (Error 3492)

The Microsoft Jet database engine attempted to update the database design at one of the replicas. There are several possible reasons why the design could not be updated, including:

•	The object you're trying to update is already open at the replica.

•	You added an enforced relationship to a replica that has a foreign key that references a nonexistent primary key.

For additional information regarding the synchronization failure, look in the MSysSchemaProb table, either at the Design Master or the replica that was the target of the synchronization.


Can't set the specified Registry parameter for the Synchronizer. (Error 3493)

You need to reconfigure the Synchronizer on your computer.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


Unable to retrieve the specified Registry parameter for the Synchronizer. (Error 3494)

You need to reconfigure the Synchronizer on your computer.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


There are no scheduled synchronizations between the two Synchronizers. (Error 3495)

The schedule between two Synchronizers has been deleted or you are attempting to set a schedule between the Synchronizer on your computer and itself. Use the Replication Manager to set the schedule with the correct Synchronizer.


Replication Manager cannot find the ExchangeID in the MSysExchangeLog table. (Error 3496)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Unable to set a schedule for the Synchronizer. (Error 3497)

There was an internal problem setting the schedule. Try again.


Can't retrieve the full path information for a member of the replica set. (Error 3499)

This is an unexpected warning. Please contact Microsoft Product Support Services for further information.


Setting an exchange with the same Synchronizer is not allowed. (Error 3500)
You cannot specify two different Synchronizers to manage the same replica. (Error 3500)

Use a valid remote Synchronizer ID in your synchronization request.


The Design Master or replica is not being managed by a Synchronizer. (Error 3502)

You are attempting to get information about the Design Master or a replica that is not managed by a Synchronizer.


The Synchronizer's Registry has no value set for the key you queried. (Error 3503)

You need to reconfigure the Synchronizer on your computer.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


The Synchronizer ID does not match an existing ID in the MSysTranspAddress table. (Error 3504)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The Synchronizer is unable to open the Synchronizer log. (Error 3506)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Failure writing to the Synchronizer log. (Error 3507)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


There is no active transport for the Synchronizer. (Error 3508)

You must reconfigure the Replication Manager.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


Could not find a valid transport for this Synchronizer. (Error 3509)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The member of the replica set you are attempting to synchronize is currently being used in another synchronization. (Error 3510)

The Design Master or a replica can be involved in only one synchronization at a time. Although you cannot initiate a second synchronization while the member is locked, you can continue using it. Wait a few minutes and try your synchronization again.


Failed to read the dropbox folder. (Error 3512)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Failed to write to the dropbox folder. (Error 3513)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer could not find any scheduled or on-demand synchronizations to process. (Error 3514)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The Microsoft Jet database engine could not read the system clock on your computer. (Error 3515)

The Microsoft Jet database engine uses your computer's system clock for certain internal processes. It tried to read the computer's clock but was not able to. Shut down and restart your computer.


Could not find transport address. (Error 3516)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer could not find any messages to process. (Error 3517)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Could not find Synchronizer in the MSysTranspAddress table. (Error 3518)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Failed to send a message. (Error 3519)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The replica name or ID does not match a currently managed member of the replica set. (Error 3520)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Two members of the replica set cannot be synchronized because there is no common point to start the synchronization. (Error 3521)

Too much time has passed since these two members of the replica set were last synchronized. The Microsoft Jet database engine cannot find a common point of reference to begin applying changes in the content or structure of the database.


Synchronizer cannot find the record of a specific synchronization in the MSysExchangeLog table. (Error 3522)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer cannot find a specific version number in the MSysSchChange table. (Error 3523)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The history of design changes in the replica does not match the history in the Design Master. (Error 3524)

The Synchronizer is unable to synchronize the two members of the replica set because the history of design (or schema) changes is different for each replica. The discrepancy in design history might be caused by either the existence of two Design Masters or because the Design Master has been restored from a backup made sometime in the past.


Synchronizer could not access the message database. (Error 3525)

The message database is not available for use by the Synchronizer. The database file may be in use by another program or user (users should not open Synchronizer message databases). Close any application that might be using the database.


The name selected for the system object is already in use. (Error 3526)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The Synchronizer or Replication Manager could not find the system object. (Error 3527)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


There is no new data in shared memory for the Synchronizer or Replication Manager to read. (Error 3528)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The Synchronizer or Replication Manager found unread data in the shared memory. The existing data will be overwritten. (Error 3529)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The Synchronizer is already serving a client. (Error 3530)

You are attempting to start a second client of the Synchronizer, but the Synchronizer can have only one client at a time. Identify the application or user that is already using the Synchronizer and close the application.


The wait period for an event has timed out. (Error 3531)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer could not be initialized. (Error 3532)

It is not possible to start the Synchronizer. Shut down and restart your computer. If the error persists, reconfigure the Synchronizer.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


The system object used by a process still exists after the process has stopped. (Error 3533)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer looked for a system event but did not find one to report to the client. (Error 3534)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Client has asked the Synchronizer to terminate operation. (Error 3535)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer received an invalid message for a member of the replica set that it manages. (Error 3536)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Cannot initialize Synchronizer because there are too many applications running. (Error 3538)

There are not enough system resources available to run all the open applications and to start the Synchronizer. Shut down one or more applications and try again.


A system error has occurred or your swap file has reached its limit. (Error 3539)

The Synchronizer has made a system call that resulted in an unexpected problem. Shut down, turn off, and then reboot your computer.


Your swap file has reached its limit or is corrupted. (Error 3540)

The Synchronizer has encountered an unexpected system problem. Shut down, turn off, and then reboot your computer.


Synchronizer could not be shut down properly and is still active. (Error 3541)

A programmatic request to terminate the Synchronizer was not completed successfully and the Synchronizer is still running in the background.

To terminate the Synchronizer

1	Press CTRL+ALT+DELETE to display the Close Program dialog box.

2	Click Synchronizer.

3	Click End Task.


Process stopped when attempting to terminate Synchronizer client. (Error 3542)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer has not been set up. (Error 3543)

The Synchronizer for your computer has not been set up.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.

If you are using a third-party application, obtain the Synchronizer Setup disk from the developer supporting your application.


Synchronizer is already running. (Error 3544)

Only one instance of the Synchronizer can operate at a time. Use the currently operating Synchronizer instead of starting a second Synchronizer on this computer.


The two replicas you are attempting to synchronize are from different replica sets. (Error 3545)

Replicas from different replica sets cannot be synchronized. Make sure you have selected the proper replica for synchronization.


The type of synchronization you are attempting is not valid. (Error 3546)

The requested synchronization cannot be performed because of an invalid exchange option in the Synchronize method. Use a valid synchronization type in your program.


Synchronizer could not find a replica from the correct set to complete the synchronization. (Error 3547)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


GUIDs do not match or the requested GUID could not be found. (Error 3548)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The file name you provided is too long. (Error 3549)

Use a smaller file name.


There is no index on the GUID column. (Error 3550)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Unable to delete the specified Registry parameter for the Synchronizer. (Error 3551)

You need to reconfigure the Synchronizer on your computer.

To configure the Synchronizer

1	Start Replication Manager.

2	On the Tools menu, click Configure Microsoft Replication Manager.

Follow the instructions in the wizard.


The size of the Registry parameter exceeds the maximum allowed. (Error 3552)

Each parameter in the Windows Registry has a maximum size. The setting you attempted to use exceeded the allowed maximum. Check the size limitation for the parameter you are setting.


The GUID could not be created. (Error 3553)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


All valid nicknames for replicas are already in use. (Error 3555)

You have reached the maximum number of replicas (32,768) allowed in a replica set. Start a new replica set.


Invalid path for destination dropbox folder. (Error 3556)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Invalid address for destination dropbox folder. (Error 3557)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Disk I/O error at destination dropbox folder. (Error 3558)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Failure to write because destination disk is full. (Error 3559)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The two members of the replica set you are attempting to synchronize have the same ReplicaID. (Error 3560)

Synchronize with a different target member of the replica set.


The two members of the replica set you are attempting to synchronize are both Design Masters. (Error 3561)

Delete one of the Design Masters.


Access denied at destination dropbox folder. (Error 3562)

Check to see if you have permissions for the drive where the destination dropbox folder resides.


Fatal error accessing a local dropbox folder. (Error 3563)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer can't find the source file for messages. (Error 3564)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


There is a sharing violation in the source dropbox folder because the message database is open in another application. (Error 3565)

Close the message database. Users must not open the message database directly.


Network I/O error. (Error 3566)

The communication between your computer and the network is experiencing a problem. Check to be sure your network is operating properly and that your network cable is tightly connected to your computer. Shut down, turn off, and reboot your computer.


Message in dropbox folder belongs to the wrong Synchronizer. (Error 3567)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Synchronizer could not delete a file. (Error 3568)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


This member of the replica set has been logically removed from the set and is no longer available. (Error 3569)

The member of the replica set you are attempting to use has been removed because either it has not been synchronized within the required number of days (retention period) or it has been synchronized with a second Design Master. The member should be deleted from your computer.

If there is data in the member that has not been synchronized with any other member in the replica set, manually enter that data in another member. You can determine which records have unsynchronized data by examining the s_Generation field in each table. A value of 0 in the s_Generation field indicates the record is an inserted or updated and has not been synchronized with another replica in the set. To view the s_Generation field, open Microsoft Access, go to the Tools menu, click Options, select the View tab, and then select the System Objects check box.

If the member is the Design Master, compare the structure of the replica with another replica in the set to determine whether any design changes have not been synchronized.


The attempt to set a column in a partial replica violated a rule governing partial replicas. (Error 3571)

You can't change a primary key of a table in a partial replica unless it has no references to it.


A disk I/O error occurred while reading or writing to the TEMP directory. (Error 3572)

A problem has occurred accessing the TEMP directory on your computer. Check that the path to the TEMP directory is set properly.


The ReplicaID for this member of the replica set was reassigned during a move or copy procedure. (Error 3574)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The disk drive you are attempting to write to is full. (Error 3575)

The disk drive does not have enough space to complete the operation. Delete unneeded files from the disk to create sufficient space for the operation. Make space available on the disk larger than the file you are attempting to save.


The database you are attempting to open is already in use by another application. (Error 3576)

If you are attempting to open the database in exclusive mode, it is possible that another application already has the database open. If you are attempting to open the database in shared mode, it is possible that another application has the database open in exclusive mode. Close the other applications using the database and try your request again.


Can't update replication system column. (Error 3577)

The column you are attempting to update is a system column and is read-only.


Failure to replicate database; can't determine whether the database is open in exclusive mode. (Error 3578)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


Can't open replication system table <name> because the table is already in use. (Error 3581)

The system table needed to complete this operation is already in use. Wait a few minutes and try your operation again.


Insufficient memory to complete operation. (Error 3584)

Your computer ran out of memory while trying to replicate the database. Close other applications on the computer and try the operation again.


Syntax error in partial filter expression on table <name>. (Error 3586)

Make sure you are using the correct syntax in the expression.


Invalid expression in the ReplicaFilter property. (Error 3587)

The ReplicaFilter string contains an invalid word. Check the syntax for any misspelled or missing words.


Error when evaluating the partial filter expression. (Error 3588)

This is an unexpected error. Please contact Microsoft Product Support Services for further information.


The partial filter expression contains an unknown function. (Error 3589)

Make sure you are using the correct name of the function. Also, not all functions are valid in filter expressions.


You can't replicate a password-protected database or set password protection on a replicated database. (Error 3592)

If a database password is set on the database, remove the password.


You can't change the data master attribute for the replica set. (Error 3593)

Whether a replica set allows users to change data at all replicas or only at the Design Master is determined when the database is first converted into a Design Master. After the database has been converted, the single or multiple data master attribute can't be changed.


You can't change the data master attribute for the replica set. It allows data changes only at the Design Master. (Error 3594)

Whether a replicated database allows users to change data only at the Design Master or at all replicas is determined when the database is first converted into a Design Master. After the database has been converted, the single or multiple data master attribute can't be changed.


The system tables in your replica are no longer reliable and the replica should not be used. (Error 3595)

The replica on your computer is corrupted. When the Microsoft Jet database engine repaired the replica, it may have altered one or more system tables. Delete the replica and replace it with a new replica.


Synchronizing with a non-replicated database is not allowed. The <name> database is not a Design Master or replica. (Error 3605)

You are attempting to synchronize a replicated database with a non-replicated database or to synchronize two non-replicated databases. Only replicas made from the same replicated database can be synchronized.

If one of the databases has already been replicated, use it to create your second database replica.

If neither database has been replicated, select one of the databases to be used as the Design Master for the replica set. Open that database using Microsoft Access, go to the Tools menu, point to Replication, and click Create Replica. If Microsoft Access is not available but Windows 95 Briefcase is available, drag the database into the Briefcase to create a replica. Do not attempt to replicate the second of the two original databases and then synchronize the two databases. The second database must be a replica of the first for synchronization to succeed.


The replication property you are attempting to delete is read-only and cannot be removed. (Error 3607)

Check to be sure you are deleting the correct property.


Cannot populate the replica or change the replica's filter because the replica has conflicts or data errors. (Error 3636)


Cannot use the crosstab of a non-fixed column as a subquery. (Error 3637)


A Source Controlled database cannot be made replicable. (Error 3638)


Cannot synchronize a partial replica with another partial replica. (Error 3648)


Cannot create a replica of a System database. (Error 3639)


Trappable Microsoft Jet and DAO Errors

Trappable errors from the Microsoft Jet database engine can occur while an application is running, either within the development environment or as a stand-alone executable file. You can test and respond to trappable errors using the the Error object.

Code	Message

2420	Syntax error in number.

2421	Syntax error in date.

2422	Syntax error in string.

2423	Invalid use of '.', '!', or '()'.

2424	Unknown name.

2425	Unknown function name.

2426	Function isn't available in expressions.

2427	Object has no value.

2428	Invalid arguments used with domain function.

2429	In operator without ().

2430	Between operator without And.

2431	Syntax error (missing operator).

2432	Syntax error (comma).

2433	Syntax error.

2434	Syntax error (missing operator).

2435	Extra ).

2436	Missing ), ], or Item.

2437	Invalid use of vertical bars.

2438	Syntax error.

2439	Wrong number of arguments used with function.

2440	IIF function without ().

2442	Invalid use of parentheses.

2443	Invalid use of Is operator.

2445	Expression too complex.

2446	Out of memory during calculation.

2447	Invalid use of '.', '!', or '()'.

2448	Can't set value.

3000	Reserved error <Item>; there is no message for this error.

3001	Invalid argument.

3002	Couldn't start session.

3003	Couldn't start transaction; too many transactions already nested.

3005	<Database name> isn't a valid database name.

3006	Database <name> is exclusively locked.

3007	Can’t open library database <name>.

3008	The table <name> is already opened exclusively by another user, or it is already open through the user interface and cannot be manipulated programmatically.

3009	You tried to lock a table while opening it, but the table can't be locked because it is currently in use. Wait a moment, and then try the operation again.

3010	Table <name> already exists.

3011	The Microsoft Jet database engine could not find the object <name>. Make sure the object exists and that you spell its name and the path name correctly.

3012	Object <name> already exists.

3013	Couldn't rename installable ISAM file.

3014	Can't open any more tables.

3015	<Index name> isn't an index in this table. Look in the Indexes collection of the TableDef object to determine the valid index names.

3016	Field won't fit in record.

3017	The size of a field is too long.

3018	Couldn't find field <name>.

3019	Operation invalid without a current index.

3020	Update or CancelUpdate without AddNew or Edit.

3021	No current record.

3022	The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.

3023	AddNew or Edit already used.

3024	Couldn't find file <name>.

3025	Can't open any more files.

3026	Not enough space on disk.

3027	Can't update. Database or object is read-only.

3028	Can't start your application. The workgroup information file is missing or opened exclusively by another user.

3029	Not a valid account name or password.

3030	<Account name> isn't a valid account name.

3031	Not a valid password.

3032	Can't perform this operation.

3033	You don't have the necessary permissions to use the <name> object. Have your system administrator or the person who created this object establish the appropriate permissions for you.

3034	You tried to commit or roll back a transaction without first using BeginTrans.

3036	Database has reached maximum size.

3037	Can't open any more tables or queries.

3039	Couldn't create index; too many indexes already defined.

3040	Disk I/O error during read.

3041	Can't open a database created with a previous version of your application.

3042	Out of MS-DOS file handles.

3043	Disk or network error.

3044	<Path> isn't a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

3045	Couldn't use <name>; file already in use.

3046	Couldn't save; currently locked by another user.

3047	Record is too large.

3048	Can't open any more databases.

3049	Can't open database <name>. It may not be a database that your application recognizes, or the file may be corrupt.

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

3052	MS-DOS file sharing lock count exceeded. You need to increase the number of locks installed with Share.exe.

3053	Too many client tasks.

3054	Too many Memo or OLE Object fields.

3055	Not a valid file name.

3056	Couldn't repair this database.

3057	Operation not supported on linked tables.

3058	Index or primary key can't contain a Null value.

3059	Operation canceled by user.

3060	Wrong data type for parameter <parameter>.

3061	Too few parameters. Expected <number>.

3062	Duplicate output alias <name>.

3063	Duplicate output destination <name>.

3064	Can't open action query <name>.

3065	Can't execute a select query.

3066	Query must have at least one destination field.

3067	Query input must contain at least one table or query.

3068	Not a valid alias name.

3069	The action query <name> cannot be used as a row source.

3070	The Microsoft Jet database engine does not recognize <name> as a valid field name or expression.

3071	This expression is typed incorrectly, or it is too complex to be evaluated. For example, a numeric expression may contain too many complicated elements. Try simplifying the expression by assigning parts of the expression to variables.

3073	Operation must use an updatable query.

3074	Can't repeat table name <name> in FROM clause.

3075	<Message> in query expression <expression>.

3076	<Name> in criteria expression.

3077	<Message> in expression.

3078	The Microsoft Jet database engine cannot find the input table or query <name>. Make sure it exists and that its name is spelled correctly.

3079	The specified field reference could refer to more than one table listed in the FROM clause of your SQL statement.

3080	Joined table <name> not listed in FROM clause.

3081	Can't join more than one table with the same name <name>.

3082	JOIN operation <operation> refers to a field that isn't in one of the joined tables.

3083	Can't use internal report query.

3084	Can't insert data with action query.

3085	Undefined function <name> in expression.

3086	Couldn't delete from specified tables.

3087	Too many expressions in GROUP BY clause.

3088	Too many expressions in ORDER BY clause.

3089	Too many expressions in DISTINCT output.

3090	Resultant table not allowed to have more than one AutoNumber field.

3092	Can't use HAVING clause in TRANSFORM statement.

3093	ORDER BY clause <clause> conflicts with DISTINCT.

3094	ORDER BY clause <clause> conflicts with GROUP BY clause.

3095	Can't have aggregate function in expression <expression>.

3096	Can't have aggregate function in WHERE clause <clause>.

3097	Can't have aggregate function in ORDER BY clause <clause>.

3098	Can't have aggregate function in GROUP BY clause <clause>.

3099	Can't have aggregate function in JOIN operation <operation>.

3100	Can't set field <name> in join key to Null.

3101	The Microsoft Jet database engine can't find a record in the table <name> with key matching field(s) <name>.

3102	Circular reference caused by <query reference>.

3103	Circular reference caused by alias <name> in query definition's SELECT list.

3104	Can't specify fixed column heading <value> in a crosstab query more than once.

3105	Missing destination field name in SELECT INTO statement <statement>.

3106	Missing destination field name in UPDATE statement <statement>.

3107	Record(s) can't be added; no insert permission on <name>.

3108	Record(s) can't be edited; no update permission on <name>.

3109	Record(s) can't be deleted; no delete permission on <name>.

3110	Couldn't read definitions; no read definitions permission for table or query <name>.

3111	Couldn't create; no modify design permission for table or query <name>.

3112	Record(s) can't be read; no read permission on <name>.

3113	Can't update <field name>; field not updatable.

3114	Can't include Memo or OLE Object when you select unique values <statement>.

3115	Can't have Memo or OLE Object fields in aggregate argument <statement>.

3116	Can't have Memo or OLE Object fields in criteria <criteria> for aggregate function.

3117	Can't sort on Memo or OLE Object <clause>.

3118	Can't join on Memo or OLE Object <name>.

3119	Can't group on Memo or OLE Object <clause>.

3120	Can't group on fields selected with '*' <table name>.

3121	Can't group on fields selected with '*'.

3122	You tried to execute a query that doesn't include the specified expression <name> as part of an aggregate function.

3123	Can't use '*' in crosstab query.

3124	Can't input from internal report query <name>.

3125	The database engine can't find <name>. Make sure it is a valid parameter or alias name, that it doesn't include invalid characters or punctuation, and that the name isn't too long.

3126	Invalid bracketing of name <name>.

3127	The INSERT INTO statement contains the following unknown field name: <field name>. Make sure you've typed the name correctly, and try the operation again.

3128	Specify the table containing the records you want to delete.

3129	Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'.

3130	Syntax error in DELETE statement.

3131	Syntax error in FROM clause.

3132	Syntax error in GROUP BY clause.

3133	Syntax error in HAVING clause.

3134	Syntax error in INSERT INTO statement.

3135	Syntax error in JOIN operation.

3136	The LEVEL clause includes a reserved word or argument that is misspelled or missing, or the punctuation is incorrect.

3138	Syntax error in ORDER BY clause.

3139	Syntax error in PARAMETER clause.

3140	Syntax error in PROCEDURE clause.

3141	The SELECT statement includes a reserved word or an argument name that is misspelled or missing, or the punctuation is incorrect.

3143	Syntax error in TRANSFORM statement.

3144	Syntax error in UPDATE statement.

3145	Syntax error in WHERE clause.

3146	ODBC —call failed.

3151	ODBC —connection to <name> failed.

3154	ODBC —couldn't find DLL <name>.

3155	ODBC —insert on a linked table failed.

3156	ODBC —delete on a linked table failed.

3157	ODBC —update on a linked table failed.

3158	Couldn't save record; currently locked by another user.

3159	Not a valid bookmark.

3160	Table isn't open.

3161	Couldn't decrypt file.

3162	You tried to assign the Null value to a variable that isn't a Variant data type.

3163	The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.

3164	The field can't be updated because another user or process has locked the corresponding record or table.

3165	Couldn't open .inf file.

3166	Cannot locate the requested Xbase memo file.

3167	Record is deleted.

3168	Invalid .inf file.

3169	The Microsoft Jet database engine could not execute the SQL statement because it contains a field that has an invalid data type.

3170	Couldn't find installable ISAM.

3171	Couldn't find network path or user name.

3172	Couldn't open Paradox.net.

3173	Couldn't open table 'MSysAccounts' in the workgroup information file.

3174	Couldn't open table 'MSysGroups' in the workgroup information file.

3175	Date is out of range or is in an invalid format.

3176	Couldn't open file <name>.

3177	Not a valid table name.

3179	Encountered unexpected end of file.

3180	Couldn't write to file <name>.

3181	Invalid range.

3182	Invalid file format.

3183	Not enough space on temporary disk.

3184	Couldn't execute query; couldn't find linked table.

3185	SELECT INTO on a remote database tried to produce too many fields.

3186	Couldn't save; currently locked by user <name> on machine <name>.

3187	Couldn't read; currently locked by user <name> on machine <name>.

3188	Couldn't update; currently locked by another session on this machine.

3189	Table <name> is exclusively locked by user <name> on machine <name>.

3190	Too many fields defined.

3191	Can't define field more than once.

3192	Couldn't find output table <name>.

3196	The database <database name> is already in use by another person or process. When the database is available, try the operation again.

3197	The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time.

3198	Couldn't start session.  Too many sessions already active.

3199	Couldn't find reference.

3200	The record cannot be deleted or changed because table <name> includes related records.

3201	You can't add or change a record because a related record is required in table <name>.

3202	Couldn't save; currently locked by another user.

3203	Subqueries cannot be used in the expression <expression>.

3204	Database already exists.

3205	Too many crosstab column headers <value>.

3206	Can't create a relationship between a field and itself.

3207	Operation not supported on a Paradox table with no primary key.

3208	Invalid Deleted setting in the Xbase key of the Windows Registry.

3210	The connection string is too long.

3211	The database engine couldn't lock table <name> because it's already in use by another person or process.

3212	Couldn't lock table <name>; currently in use by user <name> on machine <name>.

3213	Invalid Date setting in the Xbase key of the Windows Registry.

3214	Invalid Mark setting in the Xbase key of the Windows Registry.

3215	Too many Btrieve tasks.

3216	Parameter <name> specified where a table name is required.

3217	Parameter <name> specified where a database name is required.

3218	Couldn't update; currently locked.

3219	Invalid operation.

3220	Incorrect collating sequence.

3221	Invalid settings in the Btrieve key of the Windows Registry.

3222	Query can't contain a Database parameter.

3223	<Parameter name> is invalid because it's longer than 64 characters or contains invalid characters.

3224	Can't read Btrieve data dictionary.

3225	Encountered a record locking deadlock while performing a Btrieve operation.

3226	Errors encountered while using the Btrieve DLL.

3227	Invalid Century setting in the Xbase key of the Windows Registry.

3228	Invalid CollatingSequence setting in the Paradox key of the Windows Registry.

3229	Btrieve —can't change field.

3230	Out-of-date Paradox lock file.

3231	ODBC —field would be too long; data truncated.

3232	ODBC —couldn't create table.

3234	ODBC —remote query timeout expired.

3235	ODBC —data type not supported on server.

3238	ODBC —data out of range.

3239	Too many active users.

3240	Btrieve —missing Btrieve engine.

3241	Btrieve —out of resources.

3242	Invalid reference in SELECT statement.

3243	None of the import field names match fields in the appended table.

3244	Can't import password-protected spreadsheet.

3245	Couldn't parse field names from the first row of the import table.

3246	Operation not supported in transactions.

3247	ODBC —linked table definition has changed.

3248	Invalid NetworkAccess setting in the Windows Registry.

3249	Invalid PageTimeout setting in the Windows Registry.

3250	Couldn't build key.

3251	Operation is not supported for this type of object.

3252	Can't open a form whose underlying query contains a user-defined function that attempts to set or get the form's RecordsetClone property.

3254	ODBC —Can't lock all records.

3256	Index file not found.

3257	Syntax error in WITH OWNERACCESS OPTION declaration.

3258	The SQL statement couldn't be executed because it contains ambiguous outer joins. To force one of the joins to be performed first, create a separate query that performs the first join and then include that query in your SQL statement.

3259	Invalid field data type.

3260	Couldn't update; currently locked by user <name> on machine <name>.

3261	Table <name> is exclusively locked by user <name> on machine <name>.

3262	Couldn't lock table <name>; currently in use by user <name> on machine <name>.

3263	Invalid Database object.

3264	No field defined —cannot append TableDef or Index.

3265	Item not found in this collection.

3266	Can't append a Field that is already a part of a Fields collection.

3267	Property can be set only when the Field is part of a Recordset object's Fields collection.

3268	Can't set this property once the object is part of a collection.

3269	Can't append an Index that is already a part of an Indexes collection.

3270	Property not found.

3271	Invalid property value.

3272	Object isn't a collection.

3273	Method not applicable for this object.

3274	External table isn't in the expected format.

3275	Unexpected error from external database driver <error number>.

3276	Invalid database object reference.

3277	Can't have more than 10 fields in an index.

3278	The Microsoft Jet database engine has not been initialized.

3279	The Microsoft Jet database engine has already been initialized.

3280	Can't delete a field that is part of an index or is needed by the system.

3281	Can't delete this index or table.  It is either the current index or is used in a relationship.

3282	Operation not supported on a table that contains data.

3283	Primary key already exists.

3284	Index already exists.

3285	Invalid index definition.

3286	Format of memo file doesn't match specified external database format.

3287	Can't create index on the given field.

3288	Paradox index is not primary.

3289	Syntax error in CONSTRAINT clause.

3290	Syntax error in CREATE TABLE statement.

3291	Syntax error in CREATE INDEX statement.

3292	Syntax error in field definition.

3293	Syntax error in ALTER TABLE statement.

3294	Syntax error in DROP INDEX statement.

3295	Syntax error in DROP TABLE or DROP INDEX.

3296	Join expression not supported.

3297	Couldn't import table or query. No records found, or all records contain errors.

3298	There are several tables with that name. Please specify owner in the format 'owner.table'.

3299	ODBC Specification Conformance Error <message>. Report this error to the developer of your application.

3300	Can't create a relationship.

3301	Can't perform this operation; features in this version are not available in databases with older formats.

3302	Can't change a rule while the rules for this table are in use.

3303	Can't delete this field. It's part of one or more relationships.

3304	You must enter a personal identifier (PID) consisting of at least 4 and no more than 20 characters and digits.

3305	Invalid connection string in pass-through query.

3306	You've written a subquery that can return more than one field without using the EXISTS reserved word in the main query's FROM clause. Revise the SELECT statement of the subquery to request only one field.

3307	The number of columns in the two selected tables or queries of a union query don't match.

3308	Invalid TOP argument in select query.

3309	Property setting can't be larger than 2K.

3310	This property isn't supported for external data sources or for databases created with a previous version of Microsoft Jet.

3311	Property specified already exists.

3312	Validation rules and default values can't be placed on system or linked tables.

3313	Can't place this validation expression on this field.

3314	The field <name> can't contain a Null value because the Required property for this field is set to True. Enter a value in this field.

3315	Field <name> can't be a zero-length string.

3316	<Table-level validation text>.

3317	One or more values are prohibited by the validation rule <rule> set for <name>. Enter a value that the expression for this field can accept.

3318	Values specified in a TOP clause are not allowed in delete queries or reports.

3319	Syntax error in union query.

3320	<Error> in table-level validation expression.

3321	No database specified in connection string or IN clause.

3322	Crosstab query contains one or more invalid fixed column headings.

3323	The query cannot be used as a row source.

3324	The query is a DDL query and cannot be used as a row source.

3325	Pass-through query with ReturnsRecords property set to True did not return any records.

3326	This Recordset is not updatable.

3334	Can be present only in version 1.0 format.

3336	Btrieve: Invalid IndexDDF option in initialization setting.

3337	Invalid DataCodePage option in initialization setting.

3338	Btrieve: Xtrieve options aren't correct in initialization setting.

3339	Btrieve: Invalid IndexDeleteRenumber option in initialization setting.

3340	Query <name> is corrupt.

3341	The current field must match the join key <name> in the table that serves as the 'one' side of one-to-many relationship. Enter a record in the 'one' side table with the desired key value, and then make the entry with the desired join key in the 'many-only' table.

3342	Invalid Memo or OLE Object in subquery <name>.

3343	Unrecognized database format <filename>.

3344	The database engine does not recognize either the field <name> in a validation expression, or the default value in the table <name>.

3345	Unknown or invalid field reference <name>.

3346	Number of query values and destination fields aren't the same.

3349	Numeric field overflow.

3350	Object is invalid for operation.

3351	The ORDER BY expression <expression> includes fields that aren't selected by the query. Only those fields requested in the first query can be included in an ORDER BY expression.

3352	No destination field name in INSERT INTO statement <statement>.

3353	Btrieve: Can't find file Field.ddf.

3354	At most one record can be returned by this subquery.

3355	Syntax error in default value.

3356	You attempted to open a database that is already opened exclusively by user <name> on machine <name>. Try again when the database is available.

3357	This query is not a properly formed data-definition query.

3358	Can't open the Microsoft Jet engine workgroup information file.

3359	Pass-through query must contain at least one character.

3360	Query is too complex.

3361	Unions not allowed in a subquery.

3362	Single-row update/delete affected more than one row of a linked table. Unique index contains duplicate values.

3364	Can't use Memo or OLE Object field <name> in the SELECT clause of a union query.

3365	Can't set this property for remote objects.

3366	Can't append a relation with no fields defined.

3367	Can't append. An object with that name already exists in the collection.

3368	Relationship must be on the same number of fields with the same data types.

3370	Can't modify the design of table <name>. It's in a read-only database.

3371	Can't find table or constraint.

3372	No such index <name> on table <name>.

3373	Can't create relationship. Referenced table <name> doesn't have a primary key.

3374	The specified fields are not uniquely indexed in table <name>.

3375	Table <name> already has an index named <name>.

3376	Table <name> doesn't exist.

3377	No such relationship <name> on table <name>.

3378	There is already a relationship named <name> in the current database.

3379	Can't create relationships to enforce referential integrity. Existing data in table <name> violates referential integrity rules in table <name>.

3380	Field <name> already exists in table <name>.

3381	There is no field named <name> in table <name>.

3382	Size of field <name> is too long.

3383	Can't delete field <name>. It's part of one or more relationships.

3384	Can't delete a built-in property.

3385	User-defined properties don't support a Null value.

3386	Property <name> must be set before using this method.

3388	Unknown function <name> in validation expression or default value on <name>.

3389	Query support unavailable.

3390	Account name already exists.

3393	Can't perform join, group, sort, or indexed restriction. A value being searched or sorted on is too long.

3394	Can't save property; property is a schema property.

3396	Can't perform cascading operation. Since related records exist in table <name>, referential integrity rules would be violated.

3397	Can't perform cascading operation. There must be a related record in table <name>.

3398	Can't perform cascading operation. It would result in a null key in table <name>.

3399	Can't perform cascading operation. It would result in a duplicate key in table <name>.

3400	Can't perform cascading operation. It would result in two updates to field <name> in table <name>.

3401	Can't perform cascading operation. It would cause field <name> to become Null, which is not allowed.

3402	Can't perform cascading operation. It would cause field <name> to become a zero-length string, which is not allowed.

3403	Can't perform cascading operation: <validation text>.

3404	Can't perform cascading operation. The value entered is prohibited by the validation rule <rule> set for <name>.

3405	Error <error text> in validation rule.

3406	The expression you're trying to use for the DefaultValue property is invalid because <error text>. Use a valid expression to set this property.

3407	The server's MSysConf table exists, but is in an incorrect format. Contact your system administrator.

3409	Invalid field name <name> in definition of index or relationship.

3411	Invalid entry. Can't perform cascading operation in table <name> because the value entered is too large for field <name>.

3412	Can't perform cascading update on table <name> because it is currently in use by user <name> on machine <name>.

3414	Can't perform cascading operation on table <name> because it is currently in use.

3415	Zero-length string is valid only in a Text or Memo field.

3416	<reserved error alert>

3417	An action query cannot be used as a row source.

3418	Can't open <tablename>. Another user has the table open using a different network control file or locking style.

3419	Can't open this Paradox 4.x or 5.x table because ParadoxNetStyle is set to 3.x in the Windows Registry.

3420	Object reference is invalid or the object library isn't registered.

3421	Data type conversion error.

3422	Can't modify table structure. Another user has the table open.

3423	You cannot use ODBC to import from, export to, or link an external Microsoft Jet or ISAM database table to your database.

3424	Can't create database because the locale is invalid.

3428	A problem occurred in your database. Correct the problem by repairing and compacting the database.

3429	Incompatible version of an installable ISAM.

3430	While loading the Microsoft Excel installable ISAM, OLE was unable to initialize.

3431	This is not a Microsoft Excel 5.0 file.

3432	Error opening a Microsoft Excel 5.0 file.

3433	Invalid setting in Excel key of Engines section of the Windows Registry.

3434	Can't expand named range.

3435	Cannot delete spreadsheet cells.

3436	Failure creating file.

3437	Spreadsheet is full.

3438	The data being exported does not match the format described in the Schema.ini file.

3439	You attempted to link or import a Microsoft Word mail merge file. Although you can export such files, you cannot link or import them.

3440	An attempt was made to import or link an empty text file. To import or link a text file, the file must contain data.

3441	Text file specification field separator matches decimal separator or text delimiter.

3442	In the text file specification <name>, the <name> option is invalid.

3443	In the fixed-width specification <name>, the <name> does not specify a width.

3444	In the fixed width specification <name>, column <column> does not specify a width.

3445	Incorrect version of the DLL file <name> was found.

3446	Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) is missing. Try reinstalling the application that returned the error.

3447	The Jet VBA file (VBAJET.dll for 16-bit versions, or VBAJET32.dll for 32-bit versions) failed to initialize when called. Try reinstalling the application that returned the error.

3448	A call to an OLE system function was not successful. Try reinstalling the application that returned the error.

3449	No country code found in connection string for a linked table.

3452	You can't make changes to the design of the database at this replica.

3453	You can't establish or maintain an enforced relationship between a replicated table and a local table.

3455	Can't make the database replicable.

3456	Can't make the <name> object in <name> container replicable.

3457	You can't set the KeepLocal property for an object that is already replicated.

3458	The KeepLocal property cannot be set on a database; it can be set only on the objects in a database.

3459	After a database has been replicated, you cannot remove the replication features from the database.

3460	The operation you attempted conflicts with an existing operation involving this member of the replica set.

3461	The replication property you are attempting to set or delete is read-only and can't be changed.

3462	Failure to load a DLL.

3463	Can't find the .dll <name>.

3464	Data type mismatch in criteria expression.

3465	The disk drive you are attempting to access is unreadable.

3468	Access was denied while accessing dropbox folder <name>.

3469	The disk for dropbox folder <name> is full.

3470	Disk failure accessing dropbox folder <name>.

3471	Failure to write to the Synchronizer log file.

3472	Disk full for path <name>.

3473	Disk failure while accessing log file <name>.

3474	Can't open the log file <name> for writing.

3475	Sharing violation while attempting to open log file <name> in Deny Write mode.

3476	Invalid dropbox path <name>.

3477	Dropbox address <name> is syntactically invalid.

3478	The replica is not a partial replica.

3479	Can't designate a partial replica as the Design Master for the replica set.

3480	The relationship <name> in the partial filter expression is invalid.

3481	The table name <name> in the partial filter expression is invalid.

3482	The filter expression for the partial replica is invalid.

3483	The password supplied for the dropbox folder <name> is invalid.

3484	The password used by the Synchronizer to write to a destination dropbox folder is invalid.

3485	The object can't be replicated because the database is not replicated.

3486	You can't add a second Replication ID AutoNumber field to a table.

3487	The database you are attempting to replicate can't be converted.

3488	The value specified is not a ReplicaID for any member in the replica set.

3489	The object specified can't be replicated because it is missing a necessary resource.

3490	Can't create a new replica because the <name> object in <name> container could not be replicated.

3491	The database must be opened in exclusive mode before it can be replicated.

3492	The synchronization failed because a design change could not be applied to one of the replicas.

3493	Can't set the specified Registry parameter for the Synchronizer.

3494	Unable to retrieve the specified Registry parameter for the Synchronizer.

3495	There are no scheduled synchronizations between the two Synchronizers.

3496	Replication Manager cannot find the ExchangeID in the MSysExchangeLog table.

3497	Unable to set a schedule for the Synchronizer.

3499	Can't retrieve the full path information for a member of the replica set.

3500	Setting an exchange with the same Synchronizer is not allowed.

3502	The Design Master or replica is not being managed by a Synchronizer.

3503	The Synchronizer's Registry has no value set for the key you queried.

3504	The Synchronizer ID does not match an existing ID in the MSysTranspAddress table.

3506	The Synchronizer is unable to open the Synchronizer log.

3507	Failure writing to the Synchronizer log.

3508	There is no active transport for the Synchronizer.

3509	Could not find a valid transport for this Synchronizer.

3510	The member of the replica set you are attempting to synchronize is currently being used in another synchronization.

3512	Failed to read the dropbox folder.

3513	Failed to write to the dropbox folder.

3514	Synchronizer could not find any scheduled or on-demand synchronizations to process.

3515	The Microsoft Jet database engine could not read the system clock on your computer.

3516	Could not find transport address.

3517	Synchronizer could not find any messages to process.

3518	Could not find Synchronizer in the MSysTranspAddress table.

3519	Failed to send a message.

3520	The replica name or ID does not match a currently managed member of the replica set.

3521	Two members of the replica set cannot be synchronized because there is no common point to start the synchronization.

3522	Synchronizer cannot find the record of a specific synchronization in the MSysExchangeLog table.

3523	Synchronizer cannot find a specific version number in the MSysSchChange table.

3524	The history of design changes in the replica does not match the history in the Design Master.

3525	Synchronizer could not access the message database.

3526	The name selected for the system object is already in use.

3527	The Synchronizer or Replication Manager could not find the system object.

3528	There is no new data in shared memory for the Synchronizer or Replication Manager to read.

3529	The Synchronizer or Replication Manager found unread data in the shared memory. The existing data will be overwritten.

3530	The Synchronizer is already serving a client.

3531	The wait period for an event has timed out.

3532	Synchronizer could not be initialized.

3533	The system object used by a process still exists after the process has stopped.

3534	Synchronizer looked for a system event but did not find one to report to the client.

3535	Client has asked the Synchronizer to terminate operation.

3536	Synchronizer received an invalid message for a member of the replica set that it manages.

3538	Cannot initialize Synchronizer because there are too many applications running.

3539	A system error has occurred or your swap file has reached its limit.

3540	Your swap file has reached its limit or is corrupted.

3541	Synchronizer could not be shut down properly and is still active.

3542	Process stopped when attempting to terminate Synchronizer client.

3543	Synchronizer has not been set up.

3544	Synchronizer is already running.

3545	The two replicas you are attempting to synchronize are from different replica sets.

3546	The type of synchronization you are attempting is not valid.

3547	Synchronizer could not find a replica from the correct set to complete the synchronization.

3548	GUIDs do not match or the requested GUID could not be found.

3549	The file name you provided is too long.

3550	There is no index on the GUID column.

3551	Unable to delete the specified Registry parameter for the Synchronizer.

3552	The size of the Registry parameter exceeds the maximum allowed.

3553	The GUID could not be created.

3555	All valid nicknames for replicas are already in use.

3556	Invalid path for destination dropbox folder.

3557	Invalid address for destination dropbox folder.

3558	Disk I/O error at destination dropbox folder.

3559	Failure to write because destination disk is full.

3560	The two members of the replica set you are attempting to synchronize have the same ReplicaID.

3561	The two members of the replica set you are attempting to synchronize are both Design Masters.

3562	Access denied at destination dropbox folder.

3563	Fatal error accessing a local dropbox folder.

3564	Synchronizer can't find the source file for messages.

3565	There is a sharing violation in the source dropbox folder because the message database is open in another application.

3566	Network I/O error.

3567	Message in dropbox folder belongs to the wrong Synchronizer.

3568	Synchronizer could not delete a file.

3569	This member of the replica set has been logically removed from the set and is no longer available.

3571	The attempt to set a column in a partial replica violated a rule governing partial replicas.

3572	A disk I/O error occurred while reading or writing to the TEMP directory.

3574	The ReplicaID for this member of the replica set was reassigned during a move or copy procedure.

3575	The disk drive you are attempting to write to is full.

3576	The database you are attempting to open is already in use by another application.

3577	Can't update replication system column.

3578	Failure to replicate database; can't determine whether database is open in exclusive mode.

3581	Can't open replication system table <name> because the table is already in use.

3584	Insufficient memory to complete operation.

3586	Syntax error in partial filter expression.

3587	Invalid expression in the ReplicaFilter property.

3588	Error when evaluating the partial filter expression.

3589	The partial filter expression contains an unknown function.

3592	You can't replicate a password-protected database or set password protection on a replicated database.

3593	Can't change a replicated database from allowing data changes at the Design Master and replicas to allowing data changes only at the Design Master.

3594	Can't change a replicated database from allowing data changes only at the Design Master to allowing data changes at the Design Master and other replicas.

3595	The system tables in your replica are no longer reliable and the replica should not be used.

3605	Synchronizing with a non-replicated database is not allowed. The <name> database is not a Design Master or replica.

3607	The replication property you are attempting to delete is read-only and cannot be removed.

3608	Record length is too long for an indexed Paradox table.

3609	No unique index found for the referenced field of the primary table.

3610	Same table referenced as both the source and destination in a make-table query.

3611	Can’t execute data definition statements on linked data sources.

3612	Multi-level GROUP BY clause is not allowed in a subquery.

3613	Can’t create a relationship on linked ODBC tables.

3614	GUID not allowed in Find method criteria expression.

3615	Type mismatch in JOIN expression.

3616	Updating data in a linked table is not supported by this ISAM.

3617	Deleting data in a linked table is not supported by this ISAM.

3618	Exceptions table could not be created on import/export.

3619	Records could not be added to exceptions table.

3620	The connection for viewing your linked Microsoft Excel worksheet was lost.

3621	Can’t change password on a shared open database.

3622	You must use the dbSeeChanges option with OpenRecordset when accessing a SQL Server table that has an IDENTITY column.

3623	Cannot access the FoxPro 3.0 bound DBF file <filename>.

3624	Couldn’t read the record; currently locked by another user.

3625	The text file specification <name> does not exist. You can’t import, export, or link using the specification.

3626	The operation failed. There are too many indexes on table <name>. Delete some of the indexes on the table and try the operation again.