FIX: DAO Oracle and the NUMBER Datatype

View products that this article applies to.

This article was previously published under Q180193

Symptoms

When using DAO/Jet to access an Oracle database, you get either blank rows back in a grid or rows filled with #DEFINE (when using Access).

↑ Back to the top

Cause

This behavior is caused by DAO having a problem determining the datatype for Oracle columns defined as NUMBER.

↑ Back to the top

Resolution

This behavior is only exhibited when the Oracle columns have been defined as NUMBER. If you define the columns as NUMBER(38,0), which is the equivalent of just NUMBER, everything works as expected. When you use DAO/Jet to access an Oracle database, you need to specify the size (total digits) and precision for table columns of type NUMBER.

↑ Back to the top

Status

Microsoft has confirmed this to be a problem in the versions of Microsoft FrontPage listed at the beginning of this article. This bug was corrected in MDAC 2.1 Service Pack 2.

You can obtain the latest version of MDAC from the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/data/aa937695.aspx

↑ Back to the top

More information

This problem was identified using Visual Basic 5.0 Enterprise edition, MDAC 1.5 (see the REFERENCES section below), and Oracle 7.3. You may see different behavior with different versions of these components. Following is an example of what will work and what will fail when creating an Oracle table that will be accessed by DAO/Jet.

This Oracle table definition will fail:

      CREATE TABLE daotest (item_number NUMBER PRIMARY KEY,
                            depot_number NUMBER);

This Oracle table definition will work:

      CREATE TABLE daotest (item_number NUMBER(38,0) PRIMARY KEY,
                            depot_number NUMBER(38,0));

If you are using Access, the first example will fill your grid with #DELETE. If you are using Visual Basic/DAO, your grid will show the correct number of rows but they won't contain any data. You can still insert records but you never get the correct display.

↑ Back to the top

References

ORACLE: The Complete Reference by George Koch and Kevin Loney

For additional information, please see the following article in the Microsoft Knowledge Base:

175018� : HOWTO: Acquire and Install the Microsoft Oracle ODBC Driver

↑ Back to the top