Access 97 to Access 2002 conversion

  • Thread starter Thread starter KK
  • Start date Start date
K

KK

Hi all,

I have an app in VB which contains Acc97 as backend. I need to convert this
to Acc2002.

I think there are some data type differences in the two formats, and their
sizes also. Will it affect my app then? Do all data types of Acc 97 exist in
Acc 2002 ? Are a few deleted in the later version?

Also my app uses SQL queries to pull data from Access tables. Will it be
affected in any manner ?

Are there any such known conversion issues ?
Please suggest.
Thanks,
KK
 
You will find some tips on converting here:
http://members.iinet.net.au/~allenbrowne/ser-48.html

Access 2002 will support all of the data types available in Access 97. The
main problems that are run into are OLE/ActiveX controls and that Access
2000 and newer use ADO by default instead of DAO. DAO is still available,
but there can be some conflicts that require a very minor coding change.
Upgrading a back-end, data only, file should go smoothely; however, make a
backup copy (or 2 or 3) of the file FIRST, just in case.

The minor programing change is a change to your DIM statements. For example:

Change
Dim rst As Recordset
To
Dim rst As DAO.Recordset

This eliminates Access from using the first Recordset object it finds and
forces it to use the DAO Recordset object. If this causes a compile error,
then you'll need to set the reference to DAO. In the code window, go to
Tools|References and place a check next to Microsoft DAO 3.6 Object Library,
click Ok to exit.
 
All datatype from Access 97 exist in Access 2002. There is a size difference
in the data structure because Access 2000 and later uses Unicode which is
double byte characters on text. The conversion of data only should go fine
(without any issues). Other than having to pull more data over the network,
there should be no problem using SQL.
--

Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access
 
A "back-end" does not really need converting to latest Access
(unless you need to repair/compact of course, which may well be an issue)
(or unless you want to take advantage of new features, clearly irrelevant
here)

If you are using VB as the front end, what's the relevance exactly? Esp. since
compatibility works as far back as Access 2.0 (for data tables).

A2k onwards allows double the database size, and uses unicode (16-bit vs
"8-bit Ascii"). But it also uses unicode compression By Default, the result
being that storage is certainly more but -Nothing Like- a doubling of bits
might suggest.

To me, given a VB front-end, the question is "how are you repair/compacting
the BE?". If that's not the issue, I can't see what is.

Chris

PS in Access queries, there was a "bug" introduced in A2k, where a query with
a "Where" clause may now need Trim(Parameter) rather than just "Parameter".
It's easy to tell (your queries suddenly produce nothing), nevertheless it's a
difference between A97 & A2k which VB may or may not be prone to.
 
Back
Top