Hi Søren,
I can't shed light on the reason why MI has different error handling, but I
have a suggestion for you to "bypass" the manual answer to the error note:
I have also seen this error, when the index file is corrupted for some reason
or sometimes if I change between different MI versions. If the indexes are not
important to you, you could start by opening the TAB file as a text file and
look for columns that are indexed. Then simply remove the Index string from the
TAB file and MI will then ignore any errors related to mal-indexed tables /
columns.
Kind regards
Jacob K. Jørgensen
Watertech a/s
________________________________
Fra: [EMAIL PROTECTED] på vegne af Søren Breddam
Sendt: lø 21-01-2006 02:22
Til: MapInfo-L (E-mail)
Emne: [MI-L] Can't catch errors!?
Hi listers :-)
I've got an app that trawls through a directory and subdirectories for tab
files and then does some transformation stuff with help from a dll.
When I find a tab file, I check for existence for a map, aid, dat and qry file.
I initially also checked for a raster extension for the same tab file, but
there were to many renamed tab files...
That was the reason why I decided to open the file in MI that didn't have a
file with the above extension - and not just check for existence of a raster
extension - to track the tab type. This was good in most cases but some cases
produces an error I can't track!
The problem is about isolated tab files:
If I make an emty txt file in Notepad with a .tab extension, error handling is
ok, but if I have a backup of a tab file (like MYtabfileBAK.tab - MYtabfile.tab
and belonging files are present) I can't track the error but MI produces a
'note' that I have to discard manually (i.e. 'Can't get access to index
for...').
I can't figure out why, and my search log file would be poorer without this
feature because I would have to classify all tab file without the above
extensions as raster tab files. (Those really could be tab files with other
information stored in it. Else they are discarded as malformed...)
It's not that big a deal - my raster handling sub tracks the errors ok, but I
wont get extended information about the leftover files (about 700) which I
could get with TableInfo()...
Could anybody shed some light over this: Why is a malformed tab file handled
with error handling in MB and allows an app to proceed, when a well formed tab
file produces an error because affiliated files are not present?
Venligst
Søren Breddam
Stevns Kommune - www.stevns.dk
Vallø-Stevns fusion:
www.valloe-stevns.dk
* Tlf.: 5656 1891
* Mob.:2895 3034
_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l
_______________________________________________
MapInfo-L mailing list
[email protected]
http://www.directionsmag.com/mailman/listinfo/mapinfo-l
