On Mon, 12 Sep 2005 23:08:15 +1000, Luke Webber <luke (AT) webber (DOT) com.au>
wrote:

Yeah, but people skimming the subject threads will never see the fact
that we're arguing the realistic points of application development and
deployment instead of the non-realistic points of which DB is better.
I know that people are seeing the thread subject and saying "geez..
not another stupid SQL versus MV thread".

Glen

--
Posted via NewsDemon.com - Premium Uncensored Newsgroup Service
------->>>>>>http://www.NewsDemon.com<<<<<<------
Unlimited Access, Anonymous Accounts, Uncensored Broadband Access

Glen wrote:

At the risk of losing you on the first sentence Glen, I don't think
it's stupid to discuss the differences - I actually think it's
important. I'd put it this way:

The vast majority of the application development and deployment that is
being / has been done with Pick/MV (PickBasic code etc.) is imbedded
within the Pick/MV DBMS, whereas it is external to SQL Server. SQL
Server is a database server - Pick/MV is a database/application server.
If you want to go down the Microsoft track then you're encouraged to treat
your DBMS in the way Microsoft treats its DBMS - regardless of essential
differences.

I'd suggest that not many businesses would select a brand new, empty,
Pick/MV DBMS over SQL Server for new application development using
predominantly Microsoft tools - which will always favour Microsoft's own DBMS
products - and yet many have chosen to re-engineer their existing
Pick/MV applications using Microsoft's tools (VB in particular). If that's the
way they choose to go then OK, although I question the wisdom of that
strategy.

It makes much more sense, to me, to go with a brand new, empty, Pick/MV
DBMS if you're developing applications with a browser UI, however,
because that allows the application server aspect of the Pick/MV DBMS
to shine through - and you're not locked in to Microsoft at either client or
server. So it seems sensible to me that if a company is looking to
re-engineer existing Pick/MV applications they should also choose to go
for a browser UI.

Cheers
Mike.