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
