Nic
Who's Annie?
re your summary
1/ Correct but Admin is done via a COM object - I haven't bothered using it yet - for
small projects everyone can log in as sa
and please how long would it take you to write a passable ISQL. As there are component
for managing IB someone will write the same for MSDE (maybe me).
2/ Absolutely
3/ You are going to make me pull my teeth out and say 'Sonny I used to write software
for CPM on my Z80 with a TPA of 48k you kids don't know what it used to be like....'
Honestly I have 64M and I load Interbase Local and MSDE and Delphi 4 and still manage
to run outlook
Would you give up triggers stored procs and RI for $50 of Ram
4/ That is the MS official line and I was a bit concerned about this but if you dig
deep enough you will find ODBC mentioned
(in fact installing MSDE silently updates your MSSQL ODBC driver!! aren't MS helpful)
I think it a semantic think of 'official' vs 'preferred'
5/ I'm using the same case tool direct that I use with IB5 and MSSQL 6.5 (its a pain
but I refuse to call it SQL Server)
If you read between the line MS want access users to drop jet and use MSDE...reason
upward scalability
So friends look forward to a brave new world where accountants cobble together mission
critical databases with unlimited upward scalabilty - no longer can the IT department
say - "We can't deploy that! it's an Access Database"
(at this point I don't know wether to laugh maniacally, cry or read a Dilbert)
At this point I have to put a plug in for the case tool I use..it is the best value
piece of software I have ever bought (bar Delphi 2)
you can get a demo from http://www.case.com Basically if you want to develop models in
SQL and you are not using a case tool you are kidding yourself - hence the 17K of
scipt that I inserting in the last mail - the full DDL script for that model over 100K
what you find is that with a case tool you tend to normalise to another order - this
model was an upgrade from one I wrote in dataflex with seven tables (Dataflex! you
say.. I know I Know..I was young and it was the 80's) It now has over 50
We can supply it for $1500 to DUG users. This is not a commercial spam. I make more in
one hour than I make out of selling this but at this point i am so happy to be an SQL
only zone I feel I have to share...big hug...smile
6/ I'm not sure what you mean by Ugly - IB is hardly pretty? Or is it one of those
depreciative throw away lines that mean nothing
I must preface this with the fact that I am the biggest MS hater out (Bill WILL BE THE
FIRST AGAINST THE WALL WHEN THE REVOLUTION COMES) but we must be pragmatic after all
you guys and dolls are developing for Win32 (roll on Delphi 5 for Linux) but on an A/B
comparison between IB5 and MSSQL (and I have developed for both) MSSQL wins for the
following reasons
Another thing I console myself with is that MSSQL wasn't written by MS
a/ IB ship with the worlds worst ODBC driver if I ever see 'unsucessful metadata
update' again i'll scream. It was so bad that they changed from visigenic to intersolv
mid 5.5 and didn't tell anyone! Now you will say you can use the bde and the sqlliks
driver but were you aware that even tho it is shipped with pro you don't have the
rights to distribute it unless you have C/E or enterprise!
b/ IB has the unfortunate habit of binding everything together - can't drop a
procedure because it's used somewhere (ie in a trigger)
this make the maintenace of DB's painfull. I assume that IB is pre compiled or
tokenised..MSSQL is runtime interp which is why you can do this in mssql and not IB
declare @ProcName char(80)
select @ProcName = procedure from table where field = @parameter
exec @ProcName
c/ TransactSQL from my eval is better that the IB's language
Mind you I am only writing from experience..have you used MSSQL Nic?
Regards
Neven
-----Original Message-----
From: Nic Wise [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, September 08, 1999 9:13 PM
To: Multiple recipients of list delphi
Subject: Re: [DUG]: Reason to buy Visual Fox Pro
Which is kinda why Annie is having small kittens over it.
When it first came out, I did some research into it - here's a summary:
1) Its MSSQL7 without any front end - no admin tools, not even an ISQL
type dealie
2) It uses MSSQL7 .mdb format, so you can just copy the files over ALA
local interbase -> full interbase
3) Its memory hungry, if mine serves correct, like needing 16meg or so
just to load itself + windows + your app. Ie, get a 64meg machine. RAM
is cheap tho.
4) ADO talks to it just fine - it appears to be an MSSQL7 DB, so ADO is
really the only 'official' way to use it.
5) MS seam to recommend you develop under MSSQL, deploy using this on
small sites, and upgrade when you hit 5 users. Sounds much better than
(H)access to me :)
6) Its a good option if you need a small system and would have gone with
paradox or access otherwise. In my reading (microsoft.com/data I think)
it appeared a little toooooo cut down for my liking, tho if you have
MSSQL experience, I can't see any reason (aside from Office2K) to use
it....
Just IMO. I'd still stick with interbase for embedded jobs, but thats
just me. Even the 'total rewrite' of MSSQL7 (over 6.5) is still very
ugly (technically - the front end is all pretty which is all most
managers care about), but there again, ya gets what ya pays for.....
N
Max Renshaw-Fox wrote:
>
> It's in Office 2000 premium, and Office Developer edition allows free
> distribution too afaik. It appears to be able to attach to, and work
> concurrently with, an MSSQL7 datafile. If D5 ADO Express will drive it OK,
> especially if RDS works Out-of-the-box, it will be a useful little beastie.
>
> Max
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
application/ms-tnef
