Hi Hugh,
One idea that comes to mind is:
Let MC 2.3 run your database stack on a network server, where it can
service HTTP client requests for specific data (and the subsequent
locking of cards or data items currently being updated) in a centralized
fashion. That way, no client runs or loads the DB stack into their
machine's memory, and everyone has equal access. The stack is loaded
into the memory space of the copy of MC running on the network server.
I've never worked with record locking, and I imagine it could get hairy
as the number of clients increases. There's probably plenty of stuff
written on it if one were to look for it.
Have fun!
Phil
Hugh Senior wrote:
>
> Greetings,
>
> I have written a (substantial) database stack which is run by a standalone
> application. The client wants to serve the database over a network and have
> several people _concurrently_ enter the record data.
>
> Is concurrent stack access supported by Metacard?
> What are the limitations /requirements?
> Is there a workaround?
>
> /H
>
> Hugh Senior
> The Flexible Learning Company
> Consultant Programming
> Voice: +44 (0)1483.27 87 27
> Web: www.flexibleLearning.com
--
Phil Davis
------------------
[EMAIL PROTECTED]
