If you can wait why not use IB, as it becomes (free/Opensource) in a couple
of months time.
> -----Original Message-----
> From: Neven MacEwan [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, 11 February 2000 12:06
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: Access v Paradox
>
> Terry
>
> If you move at all look seriously at MSDE (MS SQL7)
> Reading between the lines that's what MS want you to replace Access DB's
> with
>
> Regards
> Neven
>
>
>
> ----- Original Message -----
> From: Terry Johnson <[EMAIL PROTECTED]>
> To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> Sent: Friday, 11 February 2000 11:59
> Subject: [DUG]: Access v Paradox
>
>
> Hi All,
>
> The current project I'm working on has an existing Access db containing a
> dozen or so tables. I've worked with pdox in the past with reasonable
> success, but as with most MS products, I'm a bit cautious about Access.
>
> Specifically;
>
> 1. Too many eggs, not many baskets. Being a single flat file, if you get
> that screwed up, you lose everything. Or do you? With Pdox, at least the
> various table data is isolated in separate files, so recovery is more
> probable...
>
> 2. What's the stability like? How vulnerable are Access dbs to corruption?
> Are there good tools to fix them?
>
> 3. Speed with large dbs - as the files grow, does paradox have (or lose)
> an
> edge?
>
> TIA,
> Terry
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
>
>
> --------------------------------------------------------------------------
> -
> New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
