Hi Marco
Not sure, I will keep you posted.
Marc
----- Original Message -----
From: "Marco Groeneveld" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, November 13, 2008 10:09 AM
Subject: [RBASE-L] - Re: Server based app
Hi,
Any idea if the users are going to use different PC's as frontend for the
cental database as datacloud worldwide available ?
Werbbased solutions are the idea about acesig the solution worldwide on
any
PC, Mac, Mobile with any browser like IE, Firefox, Safari, etc.
Mabe you can use also both !
Webbased for medical people on the road with Mobiles and access to the
central database
C/S for medical people behind a desktop to have all features avialable in
R:BASE
Marco.
www.gmsbv.nl
----- Original Message -----
From: "MDRD" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, November 13, 2008 5:03 PM
Subject: [RBASE-L] - Re: Server based app
Good questions Larry
I think our users would want the app to work exactly as it does on their
own computer.
Most of our users are using the db constantly, adding rows, editing rows
and printing
all day.
You have to remember my users have very little computer knowledge. I
talked to
an office the other day that was making a copy of the Icon and they
thought it was making
a backup of the data.
I will see this guy this weekend and will know more about what he wants.
Thanks
Marc
----- Original Message -----
From: "Lawrence Lustig" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[email protected]>
Sent: Thursday, November 13, 2008 9:42 AM
Subject: [RBASE-L] - Re: Server based app
<<
On more question on this server app with 100 users across the country.
If one office had a computer crash could that corrupt the data on the
server and cause problems for the 99 other users?
You have a lot of architectural decisions to make about your application
before you can even approach this question. Obviously, when designing
the architecture of an application-for-hire, no downtime should be one
of
your design principles.
The biggest questions here are:
- Are the users actually touching the database? Or are they simply
saving data in an intermediate format that's "sucked into" the database
by a server process?
- Is everybody working in a _single_ databaes instance, or do they have
their own instances? Separate instances mean less chance of spreading
problems.
- Are the users computers actually connected to the database? In a
typical web application, the computers are only actually connected for
very brief periods of time. Client server apps can be designed either
way. A terminal services application will most likely be full time
connected. The less connection time, the less chance of corruption.
--
Larry
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.2/1785 - Release Date:
11/13/2008
9:12 AM
--------------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.175 / Virus Database: 270.9.2/1785 - Release Date: 11/13/2008
9:12 AM
