Stephen Russell wrote:
> Have you considered wrapping the DB access into a series of web
> service calls?  You would get better security on your data for all of
> your clients.  You do keep a single db for all the data correct?  Or
> do you generate a new db for each client?

I thought about just one big DB for all clients, including columns in
each table to identify to which client the record belongs, but that
became too much hassle, imo, and think of the "all your eggs in one
basket" idea.  Instead, because the SQLYog tool allows me
to easily sync db structures, I keep separate databases for each client
now.  Or at least that's the planned approach.  I don't yet have a
MySQL-backend app for multiple clients yet....only the FabMate app,
which uses DBC-linked DBFs.  I did tinker with the idea of putting in
triggers/stored-procedures to sync the data to a MySQL database well as,
kind of like a mirroring effect...but I didn't pursue that (yet).

>
> Benefits are that you could present a service to do data manipulation
> on the server/database instead of bringing that data local and then
> passing it back for reseting to a new status.  I think of rolling
> status in a job from one phase to another.
>
> This is all part of working with a C/S mindset where you are
> disconnected to your data.
>

Absolutely.  I think it's best to think/design in that disconnected
dataset model.  I haven't learned ASP.Net or other web stuff yet, but I
know that my thinking in terms of disconnected datasets will help me
learn those tools easier.  I remember getting that idea from a Robert
Green (or maybe even Mr. Petersen) whitepaper back in VFP5/6 days.  Made
good sense.




_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to