Yeah my client will need it as a flat database, so running a server will
be an over kill.
The app will be running in possibly hundreds of locations and shared to
only 2 to 10 users at the time.
If RB does not have this functionality, im ok with that, I just got to
do it the old fashion way.
Matt Quagliana wrote:
On Sat, 06 Jan 2007 18:09:19 -0800, Giovanni wrote:
So what your saying is that RBDB is not multiuser and that there is
no built in mechanism in RB to lock and unlock the database
automatically?
REAL SQL Database --the database that is built into REALbasic-- is a
local, single user database. It was never intended for multiple
concurrent users. If you have a REAL SQL Database you would like to
have multiple people access concurrently, you should to use REAL SQL
Server.
REAL SQL Server is based on the same database engine as REAL SQL
Database and uses the same file format. And you use the same database
API to access either database. Because of these similarities you can
convert a REALbasic application from single user to multiuser with
relatively little effort.
More info on REAL SQL Database:
http://www.realbasic.com/products/realsqlserver/
it seems like such a waste of resources just to let 2 to 4 users
share a database.
REAL SQL Server scales up to 100s of concurrent users but it's not
unusual for someone to use to it to share data among just 3 or 4
people. That's why we have a version that supports five concurrent
connections.
--
Matt Quagliana
REAL Software, Inc.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
