Quoting Mark Derricutt <[EMAIL PROTECTED]>:
> On Wed, 3 Nov 1999, Nic Wise wrote:
>
> > Pester Corel. Inprise have nothing to do with Paradox anymore.
>
> Ah yes, I forgot they owned it now...
>
> > I'd see it as SO unlikely as to not happen. But I may be wrong :)
> > You need to go ADO -> OLE-DB(ODBC) -> ODBC (Paradox 5 driver)....
>
> Anyone know of any pitfalls I should look for if I was migrating from
> paradox with Access/ADO ??
1. Access does not have separate date and time types, just one date/time. You
would possibly have to write an event handler for TDBEdit controls that link to
date/time fields to ensure correct display/editing format.
2. Access's locking scheme is a whole different ballgame - quite apart from the
fact that it is page locked instead of record locked, Access locking from what
I can see does NOT place the lock on the record as soon as you start to edit
it, it seems to try to resolve locking when the record is posted.
3. Autonumber fields are problematic, it is not possible to read back the value
of the Autonumber unless a post and/or refresh is done first (Though from
memory Paradox is the same?)
(Have been testing with Adonis 3.3 so may not be universal)
4. The license agreement for MDAC seems to preclude its use with anything else
other than MS tools. Any comment on this from our friendly Inprise people?
Access 97 and up have a built in replication manager for managing
synchronisation of multiple copies of a database. If your client has already
got Access installed then it is a compelling rationale for going to Access if
they want to run your database on a laptop and synchronise with the server.
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
