Fallback DNCL tables should always be opened read only

[GoogleCodeExporter]

The Fallback DNCL tables should only ever be opened read-only.

Three reasons:
1. As the name suggests "fallback" is a resource of last resort. We should be 
encouraging users to have a "proper" DNCL within their particular dataset.
2. The fallback DNCL table should always work. We don't wont opening them them 
to fail because there is an existing lock on them (real or defunct).
3. By default the default DNCL tables reside in "C:\Program Files\...", hence 
are read-only to normal (ie non-admin) users. Currently if a non-admin user 
attempts to open the fallback DNCL it will fail.

Original issue reported on code.google.com by andrewphilipsmith on 14 Jul 2010 at 5:16

• Blocked on: #5

[GoogleCodeExporter]

A work-around for this has been developed. See comments on issue #5.

It is possible to read the contents of an Access DB in a read-only directory, 
if it is referred to via a DSN file. A DSN file has been added to the install 
directory. By selecting the "Built-in" option for Data Name Clause Lookup 
Table, the tool is point to this DSN file, rather then directly to the Access 
DB.

This hack provides the require functionality, but is not entirely satisfactory. 
The text box shows the path to the DSN file rather than the Access DB, which 
may be misleading or confusing to end users. 

However it is good enough to drop the priority to low.

Original comment by andrewphilipsmith on 22 Nov 2010 at 5:42

• Added labels: Priority-Low
• Removed labels: Priority-High

[GoogleCodeExporter]

Original comment by andrewphilipsmith on 4 Mar 2013 at 3:29

• Changed state: WontFix
• Now blocked on: #5