Re: Migration for MS-Access Bugs

Oracle is conveniently not pointing out two important factors:

1. The problem lies with JET, not with the persistent storage.
2. The reason that most developers use JET for dealing with desktop database formats is that *they are cheap* and do not want to incur a per seat run-time fee.

In order to bypass the problem when working with Oracle or SQL Server (et. al.), you will need to avoid using DAO/JET and recode to use ODBCDirect, RDO, ODBC API, ADO, Oracle Objects, etc. - each of which has bugs and/or limitations that you must learn to overcome.

Michael D. Long
http://www.geocities.com/siliconvalley/heights/9478/

Ng K C Paul <paulkcng_at_news.netvigator.com> wrote in article <6sj8de$hgb$1_at_imsp009a.netvigator.com>...
> Are there any migration programs other than ORACLE for MS-Access?
>
>
>
> Linkname: Oracle Provides Solution for Microsoft Access Customers
> URL: http://www.oracle.com/html/access.html
>
> - From CNET News.com: Microsoft Database Loses Records
 

>
> - Data Bug in All Versions of Access
>
> - Emergency Migration Program Helps Microsoft Access Users Move Data To
> Safe Oracle Databases
>
Received on Thu Sep 03 1998 - 00:00:00 CDT