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.

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.

Yes! We’ve made it simple to create a database that you can use to store index information and perform searches with SimpleIndex Retrieval Mode.

Once you have configured a SimpleIndex job to scan and store documents on your network, use these steps to create a database to store index information for searching:

1. On the database tab, make sure “Create Generic Access DB” is selected in the drop-down and click “Start”.

2. Save the Access database in a location accessible to all SimpleIndex users.

All the settings on this form will be filled in automatically after you save the database.

3. Change the “Database Mode” to “Insert New Records”. This means that when the job is run, new records will be added to the database as new files are processed.

4. Save the this configuration.

5. To create a configuration for searching and viewing, simply change the “Database Mode” setting to “Retrieve and View Records”.

You may wish to change field types on the Index tab to “List”. This will let the users select from a list of possible values for that field when searching.

Save this configuration to a different file and use it when searching. That’s it!