Robert L. Stewart
rl_stewart at highstream.net
Tue Nov 16 13:55:59 CST 2004
As you can see, Access and the ODBC driver has trouble with a partioned table. Use Toad or something like it for the type of things you would do in running queries and viewing data. Since it is written for Oracle, it plays with it better. Robert At 12:01 PM 11/16/2004 -0600, you wrote: >Date: Tue, 16 Nov 2004 10:28:49 -0500 >From: "O'Connor, Patricia \(OTDA\)" > <Patricia.O'Connor at dfa.state.ny.us> >Subject: [AccessD] ODBC against Oracle partitioned db >To: "Access Developers discussion and problem solving" > <accessd at databaseadvisors.com> >Message-ID: > <B94C79B465542042AB0748EAF37F9AC0A427B1 at EXCNYSM0A1AB.nysemail.nyenet> >Content-Type: text/plain; charset="us-ascii" > >Hi all > >When I use the Oracle ODBC driver against an ORACLE un-partitioned table >from Access (either passthru or gui), I have not problem. Data comes >back can scroll through 1-30+K records no problem. > >When I use same driver against an Oracle partitioned table from access, >I get temporary freeze ups when scrolling through records even scrolling >from column 1 to say col 10 on screen. It doesn't matter how many >records in set - scroll down 3-6 records - stop. Sometimes the stall can >be 2-5 minutes. > >Doesn't matter if it is the only thing running on computer. I do not >have this problem with an unpartioned set. I waste a good amount of >time waiting for access to let me back in. > >Has anyone run into this and is there a workaround or setting I need to >change in the driver configuration. My machine is Win2k, Access2k, >Oracle10 > >Thanks in advance >Patti