Dear John
With respect, I think you are mixing two issues, the original question
was to do with amount of data when one user READS a map file and you are
now mixing this with a seperate issue of multi user access.
There are several ways to tackle multi user access. I personally think
the best is to keep all non graphical data in a true multi user database
such as Oracle, Foxpro or Access ( this is also the great attraction of
MapX). Where graphical data needs to be edited then have a routine that
keeps the object variable in local memory until ready to "commit". Then
your program ( MapBasic, VB whatever ) with error trapping enabled locks
the file ( if another user has it locked error trapping retries) then
writes the change. In practice each write is a split second and a loop
in error trap will allow all users to write.
The reason your users do not immediately see changes ( but do when
refreshing ) is that local workstations do not know that the server
files have changed! WHen you refresh though they reread the files. If
this is important to you then with VB,C Delphi etc you could have a
routine that keeps record of time stamp on file and perhaps every second
looks at this and automatically refreshes screen if files have changed.
The GIS component is only a small part of the total solution and the
real power is the combination of all of the components!
Regards
Bob
In message <001001bed9b9$b759ded0$[EMAIL PROTECTED]
m>, John Brosowsky <[EMAIL PROTECTED]> writes
>I have in the past shared MapInfo tables across a server with mixed results.
>I had an MI table being maintained on a server machine and at the same time
>being viewed on client machines. The problem was that when a feature was
>moved on the server machine, the client machines would not always see it
>until the user manually refreshed the screen. This problem was intermittent
>(pointing to server issues?) and I never nailed down a pattern. This works
>much better with MapX, but MI techsupport reports that tab files are not
>meant to be shared. Eric Zittel of MI reports on the MapX discussion forum
>:
>
>Response Author: ERIC ZITTEL (MapInfo)
>Date: Wednesday, 6/23/99
>"...tabs aren't meant to be shared. You may want to move to a data solution
>that supports sharing..."
>
>Bottom line is I wouldn't mind seeing more discussion about this. I am
>curious about what other types of "data solutions that support sharing"
>people have been coming up with.
>
>John Brosowsky
>
>
>----------------------------------------------------------------------
>To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
>"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
--
Bob Young
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
