J
Josh Grameson
Can someone give me a list of the previous versions of access?
and is access II and Office 95 the same?
and is access II and Office 95 the same?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
Douglas J. Steele
The first version was Access 1.0, soon followed with Access 1.1. Next was
Access 2.0 (part of Office 4.3) That marked the end of the 16-bit versions
of Access.
The first 32-bit version was Access 95, which was part of Office 95. That
was followed by Access 97 (Office 97), Access 2000 (Office 2000), Access
2002 (Office XP) and the current version, Access 2003.
So no, Access 2 and Office 95 are not the same.
Access 2.0 (part of Office 4.3) That marked the end of the 16-bit versions
of Access.
The first 32-bit version was Access 95, which was part of Office 95. That
was followed by Access 97 (Office 97), Access 2000 (Office 2000), Access
2002 (Office XP) and the current version, Access 2003.
So no, Access 2 and Office 95 are not the same.
J
Josh Grameson
Can I run office 4.3 (access 2) on windows xp?
Is there a conversion program to convert Access 2 to Access 2000?
Is there a conversion program to convert Access 2 to Access 2000?
D
Douglas J. Steele
I know that you can run Access 2.0 on Windows XP. Not sure about any of the
other programs in Office 4.3, but I'd assume they'd work as well.
Afraid I don't have Access 2000 installed, so I'm not sure whether it's
capable of opening an Access 2.0 database and converting it. Even if it can,
though, some parts of the language have changed in between, so some of the
commands that were valid in Access 2.0 (which used Access Basic) aren't
valid in Access 2000 (which uses VBA). I know that the Access 97 Help file
has a list of Obsolete Features, but I'm not sure if that's available in
2000. The KB article http://support.microsoft.com/?id=160820 isn't nearly
detailed enough.
That's only part of the problem, though. Since you're moving from a 16-bit
world to a 32-bit one, depending on how sophisticated your Access 2.0
database was, you may have other conversion issues to contend with, ones
that Access itself can't handle. See
http://msdn.microsoft.com/library/techart/msdn_32bitapi.htm to get an idea
of what I'm talking about.
One further complication. By default, Access 2000 uses ADO, not DAO. This is
an easy fix, though. With any code module open, select Tools | References
from the menu bar, scroll through the list of available references until you
find the one for Microsoft DAO 3.6 Object Library, and select it. If you're
not going to be using ADO, uncheck the reference to Microsoft ActiveX Data
Objects 2.1 Library (Note that you'll have to do this every time you create
a new database in Access 2000)
If you have both references, you'll find that you'll need to "disambiguate"
certain declarations, because objects with the same names exist in the 2
models. For example, to ensure that you get a DAO recordset, you'll need to
use Dim rsCurr as DAO.Recordset (to guarantee an ADO recordset, you'd use
Dim rsCurr As ADODB.Recordset)
The list of objects with the same names in the 2 models is Connection,
Error, Errors, Field, Fields, Parameter, Parameters, Property, Properties
and Recordset
other programs in Office 4.3, but I'd assume they'd work as well.
Afraid I don't have Access 2000 installed, so I'm not sure whether it's
capable of opening an Access 2.0 database and converting it. Even if it can,
though, some parts of the language have changed in between, so some of the
commands that were valid in Access 2.0 (which used Access Basic) aren't
valid in Access 2000 (which uses VBA). I know that the Access 97 Help file
has a list of Obsolete Features, but I'm not sure if that's available in
2000. The KB article http://support.microsoft.com/?id=160820 isn't nearly
detailed enough.
That's only part of the problem, though. Since you're moving from a 16-bit
world to a 32-bit one, depending on how sophisticated your Access 2.0
database was, you may have other conversion issues to contend with, ones
that Access itself can't handle. See
http://msdn.microsoft.com/library/techart/msdn_32bitapi.htm to get an idea
of what I'm talking about.
One further complication. By default, Access 2000 uses ADO, not DAO. This is
an easy fix, though. With any code module open, select Tools | References
from the menu bar, scroll through the list of available references until you
find the one for Microsoft DAO 3.6 Object Library, and select it. If you're
not going to be using ADO, uncheck the reference to Microsoft ActiveX Data
Objects 2.1 Library (Note that you'll have to do this every time you create
a new database in Access 2000)
If you have both references, you'll find that you'll need to "disambiguate"
certain declarations, because objects with the same names exist in the 2
models. For example, to ensure that you get a DAO recordset, you'll need to
use Dim rsCurr as DAO.Recordset (to guarantee an ADO recordset, you'd use
Dim rsCurr As ADODB.Recordset)
The list of objects with the same names in the 2 models is Connection,
Error, Errors, Field, Fields, Parameter, Parameters, Property, Properties
and Recordset
J
Josh Grameson
thanks for your good information.
Douglas J. Steele said:I know that you can run Access 2.0 on Windows XP. Not sure about any of the
other programs in Office 4.3, but I'd assume they'd work as well.
Afraid I don't have Access 2000 installed, so I'm not sure whether it's
capable of opening an Access 2.0 database and converting it. Even if it
can, though, some parts of the language have changed in between, so some
of the commands that were valid in Access 2.0 (which used Access Basic)
aren't valid in Access 2000 (which uses VBA). I know that the Access 97
Help file has a list of Obsolete Features, but I'm not sure if that's
available in 2000. The KB article http://support.microsoft.com/?id=160820
isn't nearly detailed enough.
That's only part of the problem, though. Since you're moving from a 16-bit
world to a 32-bit one, depending on how sophisticated your Access 2.0
database was, you may have other conversion issues to contend with, ones
that Access itself can't handle. See
http://msdn.microsoft.com/library/techart/msdn_32bitapi.htm to get an idea
of what I'm talking about.
One further complication. By default, Access 2000 uses ADO, not DAO. This
is an easy fix, though. With any code module open, select Tools |
References from the menu bar, scroll through the list of available
references until you find the one for Microsoft DAO 3.6 Object Library,
and select it. If you're not going to be using ADO, uncheck the reference
to Microsoft ActiveX Data Objects 2.1 Library (Note that you'll have to do
this every time you create a new database in Access 2000)
If you have both references, you'll find that you'll need to
"disambiguate" certain declarations, because objects with the same names
exist in the 2 models. For example, to ensure that you get a DAO
recordset, you'll need to use Dim rsCurr as DAO.Recordset (to guarantee an
ADO recordset, you'd use Dim rsCurr As ADODB.Recordset)
The list of objects with the same names in the 2 models is Connection,
Error, Errors, Field, Fields, Parameter, Parameters, Property, Properties
and Recordset