Wish List?
>From my perspective as a database geek, seems like the MI folk could use
some expensive consulting <grin> re: what is common practice among
multi-user applications. I appreciate that it would be "hard", especially
for the graphical (i.e., obj) parts of a layer, but it's important.
The multi-user issue is a big one for my firm, where we often have 3-4
engineers trying to work on maps, databases and hydraulic models during
project crunch times. We usually just make copies, and agree which one is
the "live" one. Too error prone for my taste, also it works only because
most people are just referencing the maps, not trying to update or add to
them by that point in the project.
-----Original Message-----
From: Bill Thoen [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 02, 1999 12:51 PM
To: MapInfo-L
Subject: SUM: MI How to handle multi-user in Mapbasic apps?
A couple of weeks ago I asked for advice on how to build in
multi-user user support for tables in a mapbasic application I'm
considering.
<clip>
Unfortunately, there's few good answers.
<clip>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
