Help on Access... 2.0! Really! And on 2003...

[Themis Papassilekas]

So, I don't know how tricky this is, but thought I'd ask...

Here in the office there's an inventory db that was written in Access 2.0.
Nobody cared to upgrade it since its creation back in an era long gone
-only additions were made that make the SQL code look VERY chaotic -at
least to me, and I'm not exactly a connoisseur anyway.

Anyhow, I was wondering if there's an easy way to:

a. make it run under some newer version and
b. to create a report that will check which items have changed in
quantities over the last calendar year (but it should not check wether
Qx<>Qy -this would be easy even for me, but quantities may match at the end
of the year even thought they have been changed during it).

I've also started working with Access 2003 and have a couple of questions
as well: first, why does it give me the Security Warning according to which
it requires MS Jet 4.0SP8 even if I have downloaded and installed it as
described in the related article?
And, last, how can I assign numerical (?) values to alphanumeric ones so
that a report can sort those alphanumeric values according to a preset
order -not alphabetically?

Thanks for your patience and help... Any little bit will be appreciated :)

Cheers
Themis
--
Reality is that, which, when you stop believing in it, doesn't go away
--P.K.Dick
(http://gryzor.info - remove "stopspam" from email address to reach me)

[Larry Linson]

If you want to create new reports in an Access 2.0 database, you'll need to
do it in Access 2.0, or convert the DB to a later version. From Access
versions (at least) through Access 2000, you can link to tables in the
Access 2.0 database using Get External Data | Link on the File menu, and
create reports in a database using the more recent version of Access.

IIRC, you can no longer convert Access 2.0 to current in Access 2003, but
you can in Access 95, 97, 2000, and 2002.

The only difficulty I ever had in converting an Access 2.0 database was when
it used API references to the 16-bit Windows 3.x APIs -- those had to be
updated to call the 32-bit Windows 9x, NT, 2000, or 2003 APIs. There are a
few other things that will have to be changed, but not many, and perhaps
none in any given database.

Larry Linson
Microsoft Access MVP
"Themis Papassilekas" <gr************@gryzor.info> wrote in message
news:d5**************@gryzor.info...

So, I don't know how tricky this is, but thought I'd ask...

Here in the office there's an inventory db that was written in Access 2.0.
Nobody cared to upgrade it since its creation back in an era long gone
-only additions were made that make the SQL code look VERY chaotic -at
least to me, and I'm not exactly a connoisseur anyway.

Anyhow, I was wondering if there's an easy way to:

a. make it run under some newer version and
b. to create a report that will check which items have changed in
quantities over the last calendar year (but it should not check wether
Qx<>Qy -this would be easy even for me, but quantities may match at the end of the year even thought they have been changed during it).

I've also started working with Access 2003 and have a couple of questions
as well: first, why does it give me the Security Warning according to which it requires MS Jet 4.0SP8 even if I have downloaded and installed it as
described in the related article?
And, last, how can I assign numerical (?) values to alphanumeric ones so
that a report can sort those alphanumeric values according to a preset
order -not alphabetically?

Thanks for your patience and help... Any little bit will be appreciated :)

Cheers
Themis
--
Reality is that, which, when you stop believing in it, doesn't go away
--P.K.Dick
(http://gryzor.info - remove "stopspam" from email address to reach me)

[Themis Papassilekas]

Thanks for your advice, Larry. I'll try an earlier Access version to
convert it, although I'm pretty sure I tried to do it with Access XP and
the code did not convert ok...

Any advice on my other questions, anyone? :)

Cheers
Themis

On Fri, 12 Dec 2003 22:35:08 GMT, Larry Linson wrote:

If you want to create new reports in an Access 2.0 database, you'll need to
do it in Access 2.0, or convert the DB to a later version. From Access
versions (at least) through Access 2000, you can link to tables in the
Access 2.0 database using Get External Data | Link on the File menu, and
create reports in a database using the more recent version of Access.

IIRC, you can no longer convert Access 2.0 to current in Access 2003, but
you can in Access 95, 97, 2000, and 2002.

The only difficulty I ever had in converting an Access 2.0 database was when
it used API references to the 16-bit Windows 3.x APIs -- those had to be
updated to call the 32-bit Windows 9x, NT, 2000, or 2003 APIs. There are a
few other things that will have to be changed, but not many, and perhaps
none in any given database.

Larry Linson
Microsoft Access MVP

--
Reality is that, which, when you stop believing in it, doesn't go away
--P.K.Dick
(http://gryzor.info - remove "stopspam" from email address to reach me)