Re: Compatbility of Microsoft Access 97 with Oracle 8

Hi

We had this problem about 4-5 years ago still with Access 2.0, and we had to use number(9) for integer fields on server side (counters-autonumbers usually). I did migration through reengineering Access database into Errwin, changing integer datatypes into number(9) and copied data(with help of the same Access). We are still using Intersolv drivers for Oracle 7 against 8.1.5 database and Access 97, some years ago they showed the best perfomance.
If that precicion (number(9)) is enaugh for you, try it. But, it seems to me, latest 8.1.5-8.1.6 Oracle ODBC are more correct(it seems they recognize NUMBER datatype as double or like that), but now I am not at work to say yu definitely,sorry! Try them himself! To tell the truth (that my point of view), too large systems with Access and Oracle are boring for servicing and they consume too many cursors, and very often Access deside to process statements locally, what cause full table scans and excessive network traffic, so developers should have some experience.

Oleg Fedorenkov, IT consultant

<rgbautista_at_hotmail.com> wrote in message news:8lm1h0$bn$1_at_nnrp1.deja.com...
> I have read somwhere that the Oracle Migration Assistant for Microsoft
> Access is incompatible with Microsoft Access 97 databases. I always
> encounter an error: A serious internal error has occured 440 whenever
> migration begins.
>
> Another thing is whenever I exported a Microsoft Access 97 table that
> contains number fields (single or double precision) though the Oracle
> ODBC, Oracle always converts these fields to VARCHAR. I tried changing
> them manually through the Schema Manager but the program does allow me
> to because it contains data.
>
> Can anyone verify this? Is there a simple solution to this?
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Sat Aug 12 2000 - 00:00:00 CDT