| · | Clips are saved to the database immediately when captured or edited. No more "auto-save" or "save all clips to disk" woes.
|
| · | Appreciable memory savings when you have large numbers of clips*.
|
| · | More efficient use of hard disk space. We use about a dozen files now, instead of hundreds or thousands of little files. Cluster waste is eliminated, as are "orphan" data files.
|
| · | Images are stored in the database as JPEG objects, further reducing space and speeding retrieval. (Note: "best quality" mode is used for JPEG compression)
|
| · | Searching is now very fast and much more flexible.
|
| · | Deleted clips are held in "trashcan" status for two weeks, allowing easy retrieval.
|
| · | Configuration is easy - no drivers, ODBC connections, DLLs, or connection strings.
|
| · | Will easily hold thousands of clips.
|
| · | ODBC support will be provided later this year, allowing advanced users to access or interface with the database directly. Our design will be made available to such users.
|
For more information see: Database
* We routinely test with upwards of 25,000 clips.