By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,649 Members | 1,572 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,649 IT Pros & Developers. It's quick & easy.

Linked table via ODBC

P: n/a
Ian
We are currently experiencing problems with our Access XP database. We
are using access as the front-end and are connecting to Oracle 7.3 via
ODBC. Our users are running Win 98 and Win Xp.
We are currently using Oracle73 drivers ver:1.15.03.01 File:
SQ032.73.dll Date:18/06/1996.

The Problem,
I can re-link the Oracle tables and open them within access, However
the tables take around a minute to open.
When I try to run a query I receive an error,
ODBC Call Failed
[Microsoft][ODBC Driver Manager] Memory Allocation failure (#0).

The query I am running is only a simple query, however when I make it
even simpler i.e. (Select * from table) the results are displayed but
then vanish when you scroll down the page leaving #Name? displaying in
every field.

I have just downloaded Oracle7 ODBC Driver Version 2.5.3.1.7 but am
still getting the same problem.

Any ideals or suggestions would be great. Many thanks in advance,
Ian
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Microsoft does not recommend opening linked tables by using the table
object in the database window. Queries are better - especially
queries with criteria (so as not to return the entire contents of a
table).

I've found that relinks/refreshes for remote ODBC tables sometimes
take over a minute per table on LANs/WANs.

The description of the results of your simple query seems to indicate
a slow response from Oracle or the Cache size needs to be changed.
Cache Size determines how many records are returned from the server.
See the Access help article on "CacheSize Property" (both DAO & ADO -
ADO info is in the VBA help articles "Cache size").

Also, in the past I believe there were some problems using the Oracle
ODBC drivers. I believe it was recommended that the Microsoft drivers
be used instead of the Oracle drivers. The Microsoft drivers should
be listed under the ODBC Administrator dialog box "Drivers" tab.

HTH,

MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQARMa4echKqOuFEgEQKkFwCgkRoA4B71csMqN25AtComaE c3AQgAn2Jt
k+lz+p7/ZVs3EGhqfJPGT+xK
=GlOb
-----END PGP SIGNATURE-----
Ian wrote:
We are currently experiencing problems with our Access XP database. We
are using access as the front-end and are connecting to Oracle 7.3 via
ODBC. Our users are running Win 98 and Win Xp.
We are currently using Oracle73 drivers ver:1.15.03.01 File:
SQ032.73.dll Date:18/06/1996.

The Problem,
I can re-link the Oracle tables and open them within access, However
the tables take around a minute to open.
When I try to run a query I receive an error,
ODBC Call Failed
[Microsoft][ODBC Driver Manager] Memory Allocation failure (#0).

The query I am running is only a simple query, however when I make it
even simpler i.e. (Select * from table) the results are displayed but
then vanish when you scroll down the page leaving #Name? displaying in
every field.

I have just downloaded Oracle7 ODBC Driver Version 2.5.3.1.7 but am
still getting the same problem.

Any ideals or suggestions would be great. Many thanks in advance,
Ian


Nov 12 '05 #2

P: n/a
Try including/exposing a timestamp field in that table.

I don't know if they help with Oracle, but jet does like/want those
timestamp fields when using a sub-form, or a continues form with sql server.

Give it a try, and post back here for future reference....
--
Albert D. Kallal (access MVP)
Edmonton, Alberta Canada
No************@msn.com
http://www.attcanada.net/~kallal.msn
Nov 12 '05 #3

P: n/a
Ian
I have now found a work around to my problem. I found that one of the
fields I was querying had the LONG data type. When viewing design view
for the linked table I found that Access made the field MEMO. Anyway
once I removed the field from my query it seemed to work ok.
I'm not sure why the LONG data type doesnt work correctly in Access XP
but it works when you use it in Access 95.

Anyway thanks for all your help,
regards
ian
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.