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

97 link to 2003

P: n/a
is there any way to link a Access97 database to 2003 data?

Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
No, but you can go the other way.

Convert the data file to Access 97, and then both A97 clients and A2003
clients can use it.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

<dy****@yahoo.com> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...
is there any way to link a Access97 database to 2003 data?

Nov 13 '05 #2

P: n/a
The problem is that the data is growing to higher than 1 gig. the
program is 97 and CANNOT be converted for various reasons.. is there a
ODBC that can connect 97 program to 2003 data - so that we can go to 2
gig?

Nov 13 '05 #3

P: n/a
<dy****@yahoo.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
The problem is that the data is growing to higher than 1 gig. the
program is 97 and CANNOT be converted for various reasons.. is there a
ODBC that can connect 97 program to 2003 data - so that we can go to 2
gig?


Not really. You can't use ODBC from Jet to Jet (i.e.: from one MDB to
another)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)

Nov 13 '05 #4

P: n/a
If the large data is due to binary fields (e.g. graphics), you could
probably work around the problem by hyperlinking the data instead of
embedding it.

Unless all this data is in a single table, you could work around the problem
by using multiple mdb's. You lose the referential integrity between the
tables that are split, so there you need extra code to maintain that, but
otherwise it works seemlessly.

In general, A2000 is less efficient at storing data than A97, so you
probably won't gain much storage space even if you do convert. (There are
some ways to address that such as Unicode Compression.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Douglas J. Steele" <NOSPAM_djsteele@NOSPAM_canada.com> wrote in message
news:au********************@rogers.com...
<dy****@yahoo.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
The problem is that the data is growing to higher than 1 gig. the
program is 97 and CANNOT be converted for various reasons.. is there a
ODBC that can connect 97 program to 2003 data - so that we can go to 2
gig?


Not really. You can't use ODBC from Jet to Jet (i.e.: from one MDB to
another)

Nov 13 '05 #5

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote in
news:42***********************@per-qv1-newsreader-01.iinet.net.au:
Unless all this data is in a single table, you could work around
the problem by using multiple mdb's. You lose the referential
integrity between the tables that are split, so there you need
extra code to maintain that, but otherwise it works seemlessly.


Joins are also much slower between tables in different MDBs. If
you're decomposing a widely used single table, this can be a
significant performance hit, and it might make more sense to pull up
the data from the side table one record at a time only when
requested, rather than using a recordsource with a join that
attempts to replicate the former monolithic table.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.