Unprecedented Control of Database Interactions
Open database integration is a powerful feature of SimpleIndex® and one that furthers its interoperability with custom programs. Instead of using a proprietary database, SimpleIndex allows you to map its index fields to cells in any database table. It can be configured to create new records, update existing ones or retrieve them for viewing. Using these three basic database functions, SimpleIndex is able to interface with and operate on any database.
Automatic Indexing Using Existing Data
The Autofill feature of SimpleIndex is an easy way to associate many index fields with one document without retyping data that already exists in another database. Autofill uses a database lookup to retrieve records that match a key value entered by the user. Blank index fields are then filled in automatically with the data from this lookup. The result is a document database with many different possible search fields, of which only one needed to be entered during scanning.
The key field may be typed by the user, or it may be read from the document automatically using barcode recognition or OCR. The lookup is performed either when the user changes this field or when the index values are saved. If the lookup finds multiple matching records, the user will be notified and the first set of values will be used by default.
You can find sample formats of the command lines for Simple Software products below.
“C:\Program Files (x86)\SimpleIndex\SimpleIndex.exe” /c:”Path to job file”
“C:\Program Files (x86)\SimpleIndex\SimpleSend.exe” “Path to job file” /hide /run
“C:\Program Files (x86)\SimpleIndex\qb\SimpleQB.exe” “Path to job file” /hide /run
This is used to closed SimpleIndex after the job has been completed automatically.
Put this in the Post-Proc field under the Batch tab in the Job Options:
taskkill -f -im simpleindex.exe
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.
There are a variety of ways to connect to your database. Detailed instructions are provided in the Manual (check the Help menu). Here is a brief overview of the steps involved: -Create a job configuration to scan and index files -On the database tab, set the “Database Mode” to “Insert New Records” -To use ODBC, enter the data source name or file in Data Source -To connect directly, select your database type under “Select a Data Source” and click Start. A series of dialogs will prompt you for database connection information. -Select destination Table or View and click Reload -For each index field, select the corresponding database field that will receive that field value -The “Output File Field” will receive the path to the exported file Once you have created records in your database in “Insert” mode, you can change to “Retrieve and View Records” and use SimpleIndex or SimpleSearch to search and view the files.
Can SimpleQB be used to scan in receipts and invoices which are then matched to the files kept in the QuickBooks System?
Yes, That is exactly what SimpleQB was designed to do.
SimpleQB uses the information from your QuickBooks documents to file images under the appropriate customer/vendor, document type, document number and date. Simply pull up the corresponding file in QuickBooks and click scan!
Yes. Image files can be inserted into binary fields in Access, SQL Server, Oracle, MySQL and other databases.
Check the “Store files as binary objects” option on the Database tab and the “Output File Field” setting can be mapped to a binary field.
If using PDF, MS Office or other non-image files, use the File Type Field to store the file extension of the stored file.
SimpleSearch mode will let you view files stored using this method as well.
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 there dropdown in the lower portion of the panel for Full Text OCR Field. Put the name of the field that will store the full-text data there. This must be configured both for Insert and Retrieval mode configurations. The database field needs to be sufficient length to store the entire text of your document. Of course, the Insert Mode configuration must have “Enable Full Page OCR” checked to generate full text data from images. Text from MS Office documents, PDF files and existing OCR text files can be used without setting this option. When designing your Retrieval Mode configuration, create a Text field to use for full text search queries. On the Database tab, set the corresponding “Database Field Name” to the full text database field. When searching on your full text field, SimpleIndex finds the text you enter no matter where it appears in the document. It is able to match partial words. It does not perform boolean or natural language search
Match & Attach mode lets you batch update multiple records in a database using the index data from your SimpleIndex job. For example, if you have a large backfile of documents that you want to scan and link to records in an existing database, you can use Match & Attach to find the corresponding record and set the Image Path field to the newly scanned file.
For details on how to configure Match & Attach mode, please refer to the manual.
The Autofill feature of SimpleIndex is an easy way to associate many index fields with one document without retyping data that already exists in another application. Autofill uses a database lookup to retrieve records that match a key value entered by the user. Blank index fields are then filled in automatically with the data from this lookup. The result is a document database with many different possible search fields, of which only one needed to be entered during scanning. To configure the Autofill feature first go to the Index tab and define the field that will be used to perform the lookup. Each value in this field should correspond to a single record in the database, usually defined as the “Primary Key”. This field can be any type, including Barcode and OCR for full automation. Next click “Configure Index Autofill” button. Here is where you will setup the database lookup. The “Match Data Source” is configured the same way as the “Data Sour
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.
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