In SQL Server, Oracle and MySQL (among others) user logons are associated with a default “schema” that determines which tables and views they can see.

Users may have access to other tables and views that aren’t in their schema. When connecting to the database these tables will show up in the list, but when you try to get the list of fields you get an “Invalid object reference” error.

To reference these tables, use [Schema].[Table] for the table name to explicitly reference the table.

You can also change the user’s default schema on the server to the one matching the table.

A third option is to create a view under the user’s default schema that selects the necessary records.

At the present time you cannot enter [Schema].[Table] in the wizard, so if you need to use this workaround configure the job in the wizard and modify the table name in the old job options screen.

If you would like to create a database string for an Access database that includes a password use this format:

Provider=Microsoft.Jet.OLEDB.4.0;Data Source=path\database.mdb;Jet OLEDB:Database Password=db_password;

This error is usually caused when the data you are trying to insert does not match the data type of the database field. This could be a text value being inserted into a number or date field, or a text value that is longer than the maximum length of the field.

To avoid this error, be sure to use the correct Field Type and/or Template on the Index tab to force the user to enter data in the correct format. You may also need to adjust the data types or lengths for your database fields.

If the database you use to store index information has security access features, you can use these to manage access to documents with SimpleIndex retrieval mode.

In your database, create user accounts and groups and assign them the appropriate permissions to records in your document database.

In SimpleIndex, check the “Require Logon” option on the Logging tab to force the user to logon to the database using the accounts you created. When they search and view documents, they will only be able to access records that the corresponding database user has been assigned access to.

On the Database tab, choose “SQL Server” from the drop-down labeled “Configure Data Source”. Click the “Start” button.

You will be prompted to enter the SQL Server name and database name. Once selected, an OLE DB data source will be entered under “Data Source”.

You can add a default user to the “Data Source” using the conventions for OLE DB provider strings. With this configuration, all users will use the same SQL Server login. To configure individual logins, check “Require Logon” on the Logging tab. If you would like the users to select their name from a list, add each user ID using the “Add User” button.

To connect to an existing Access database go to Options then the Database tab. There is a drop-down list next to the “Start” button. Click the arrow and select “MS Access” then click “Start”.

An Open Database dialog will be displayed. Select the Access MDB you want to use then click “Open”.

Select the table or query you want to use from the “Table Name” list and click “Reload”.

The field selectors will now be populated with the list of fields from the table/query you selected. The Image Path stores the path to the image file for each record. Each entry in Database Fields list maps the corresponding Field # from the Index tab to the selected field in the database.

Click apply and your Access Database will be configured.

The Log Field, Log Table, Revision Field/Level and the Full Text and PageCount fields on the Advanced tab are option. See the manual for a description of what these items do.