Interesting...
I just tried this (on Mapinfo 6.5 running on Windows 2000) and it worked
fine. So it looks like the proble may be with Mapinfo 7?
"Andrew Harfoot"
<[EMAIL PROTECTED] To: Wotzhere <[EMAIL PROTECTED]>
on.ac.uk> cc: "MapInfo List" <[EMAIL
PROTECTED]>
Subject: Re: MI-L "Unable to update
table xxx"
21/10/2004 12:54
Hi
The error reported when the table is saved is as follows:
'Unable to update table xxxx, Operation cancelled'
It doesn't cause the Mapinfo session to end, just deletes the transaction
files for the table currently being edited. The transaction files would be
deleted if the save proceeded according to plan, once the changes had been
written to the base table files. It looks like the process is being
interrupted by the error such that the transaction files are deleted
before the base table is updated, and the edits are lost.
To be more precise about the sequence of actions that produces the error,
I have written a workspace appended below:
!Workspace
!Version 650
!Charset WindowsLatin1
create table tabCheck (ID integer) file tempfilename$("")
create map for tabCheck
insert into tabcheck (obj) values (mbr(createline(0,0,2,2)))
insert into tabcheck (obj) values (mbr(createline(1,1,3,3)))
commit table tabcheck
map from tabCheck
set map zoom entire layer tabcheck layer tabcheck editable on
note "Two overlapping objects created"
select * from tabCheck where rowid=1 into temp
set target on
select * from tabCheck where rowid=2 into temp
note "First object set to be a target, second object selected"
objects erase into target
note "Erase operation performed"
delete from selection
Note "New object deleted"
run menu command 201
Note "Deletion undone"
commit table tabCheck
After the final "Deletion undone" message, the workspace attempts to save
the changes to the table. At this point, the error message should appear.
Andrew
On Thu, 21 Oct 2004 08:39:35 +1000, Wotzhere <[EMAIL PROTECTED]> wrote:
> Hi,
>
> When you say you get an error, are we talking about a MapInfo.exe error
> and MapInfo closes losing all data, or just an error - cannot save
> table? I do what you say quiet a lot, and had one instance on XP that
> caused so many crashes that I wrote my own cutter tool function. I am
> convinced the problem there the issue was selection of the records
> created in the table to get rid of the debris left behind by the
> standard mapbasic cutter function. There is a possible connection.
>
> r
>
> On Wed, 20 Oct 2004 11:18:22 +0100, Andrew Harfoot
> <[EMAIL PROTECTED]> wrote:
>
>> Hi Sarah & List
>>
>> I have managed to reproduce an error very similar to this consistently
>> in MI Pro 7.0 and 7.8 with the following sequence of actions:
>>
>> Create a new, mappable table, make it editable
>>
>> 1. Draw a region
>> 2. Draw another 'cutter' region that partially or completely overlaps
>> the first
>> 3. Set the first region as a target, and 'Erase' using the cutter region
>> 4. Delete the resulting modified region
>> 5. Undo the deletion
>> 6. Attempt to save the table
>>
>> The error message is produced, and all unsaved data is lost
>> (transaction files are wiped)
>>
>> The key operation appears to be the undoing of the deletion (or other
>> modification?) of an unsaved object that has been generated by Mapinfo
>> in an object modification (eg Erase, Split, Combine etc. - these all
>> delete the target objects and insert new ones into the table) as
>> opposed to a user generated polygon.
>> Significantly, (I think) if the table is saved between steps 3 and 4
>> then the error does not arise.
>> I have reproduced the error on three different machines, running
>> Windows XP and 2000 and MI 7.0 (build 26) and 7.8. The error does not
>> occur on MI Pro 6.0.
>>
>> Sarah - do you think this is the same bug, if so, you might want to
>> avoid using the undo tool when performing object manipulation
>> operations.
>>
>> Andrew
>>
>> On Tue, 19 Oct 2004 09:02:35 +0100, GIS Helpdesk
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Error Message "Unable to update Table xxx" (xxx=name of table)
>>>
>>> Using MapInfo 7.5
>>> Windows 2000
>>> Novell Network Netware 5.1, Service Pack SP5
>>> MapInfo installed from snapsot across network.
>>>
>>> Error message when table is saved. Error message then occurs, and then
>>> the polygon is lost. Or alternatively it seems to wipe several saves.
>>>
>>> Have tried the following :
>>>
>>> 1) getting rid of MapInfo on machine, and reinstalling from disk.
>>> 2) Working through desktop only, not on network.
>>> 3) Checking polygons arn't exceedingthe amount of nodes in a complex
>>> polygon.
>>> 4) Clearing out the temp directory
>>> 5) changing and checking the temporary environment variable to a local
>>> directory.
>>> 6) Fast edit is on via map basic window.
>>> 7) Looked at Novell Netware site and set client file caching = OFF on
>>> server.
>>> 8) The users appending data to rather than copying and pasting
>>> 9) Checked there is plenty of virtual memory.
>>> 10) Turned of fire wall software on the pc.
>>> 11) Turned of notification of e-mails etc.
>>>
>>> And now ......,, i am totally out of ideas, can anyone suggest
>>> anything please.
>>>
>>> THamks, Sarah
>>> [EMAIL PROTECTED]
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> List hosting provided by Directions Magazine | www.directionsmag.com |
>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>> Message number: 13758
>>
>>
>>
>
>
>
--
----------------------
Andrew Harfoot
Geodata Institute
University of Southampton
tel: +44 (0) 23 80592719
fax: +44 (0) 23 80592849
[EMAIL PROTECTED]
---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 13796
---------------------------------------------------------------------
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message number: 13797
