If i have code that works in Acess2000 but when converted to Access 97 it
doesn't, is this likely to be a missing reference? I think the line was
something like DAO.RecordSet.clone but I'm not at the Access97 machine at the
moment. It certainly had something to do with DAO and an unknown method.

Dave

OK, it appears Access 97 doesn't support any reference to DAO.Recordset. Is
this a Jet 4.0 only feature? The Access 97 machine does have a reference to
DAO 3.6.

Thanks

Dave

"David M C" wrote:

> If i have code that works in Acess2000 but when converted to Access 97 it
> doesn't, is this likely to be a missing reference? I think the line was
> something like DAO.RecordSet.clone but I'm not at the Access97 machine at the
> moment. It certainly had something to do with DAO and an unknown method.
>
> Dave

DAO 3.6 is the wrong version for Access 97, you should have a reference to
DAO 3.51

The Recordset object has been supported at least since Access 2. (I can't
comment on Access 1, as I never used it).

If you're still having problems after changing the reference to DAO 3.51,
please post the relevant code and a description of what happens when you try
to execute the code, including the exact text of any error messages and the
error number if any.

I do not recommend converting from a later version to Access 97 except in an
emergency, i.e. when a user has accidentally converted their only copy of an
MDB without realizing the consequences. I definitely do not recommend it as
a standard practise.

--
Brendan Reynolds
Access MVP

"David M C" <(E-Mail Removed)> wrote in message
news:57F9AE74-FED2-4F5D-88EB-(E-Mail Removed)...
> OK, it appears Access 97 doesn't support any reference to DAO.Recordset.
> Is
> this a Jet 4.0 only feature? The Access 97 machine does have a reference
> to
> DAO 3.6.
>
> Thanks
>
> Dave
>
> "David M C" wrote:
>
>> If i have code that works in Acess2000 but when converted to Access 97 it
>> doesn't, is this likely to be a missing reference? I think the line was
>> something like DAO.RecordSet.clone but I'm not at the Access97 machine at
>> the
>> moment. It certainly had something to do with DAO and an unknown method.
>>
>> Dave

So Access 97, even with the required DAO module, cannot use DAO 3.6?
Presumably this is due to a different version of Jet being used?

We have 1 PC that is still on Win98 and Access 97. Looks like it would be
cheaper to upgrade the PC than go through the hastle of trying to get the app
to work using Access 97. Especially since it doesn't appear to be able to
connect to an Access 2000 backend either.

Thanks

Dave

"Brendan Reynolds" wrote:

> DAO 3.6 is the wrong version for Access 97, you should have a reference to
> DAO 3.51
>
> The Recordset object has been supported at least since Access 2. (I can't
> comment on Access 1, as I never used it).
>
> If you're still having problems after changing the reference to DAO 3.51,
> please post the relevant code and a description of what happens when you try
> to execute the code, including the exact text of any error messages and the
> error number if any.
>
> I do not recommend converting from a later version to Access 97 except in an
> emergency, i.e. when a user has accidentally converted their only copy of an
> MDB without realizing the consequences. I definitely do not recommend it as
> a standard practise.
>
> --
> Brendan Reynolds
> Access MVP
>
> "David M C" <(E-Mail Removed)> wrote in message
> news:57F9AE74-FED2-4F5D-88EB-(E-Mail Removed)...
> > OK, it appears Access 97 doesn't support any reference to DAO.Recordset.
> > Is
> > this a Jet 4.0 only feature? The Access 97 machine does have a reference
> > to
> > DAO 3.6.
> >
> > Thanks
> >
> > Dave
> >
> > "David M C" wrote:
> >
> >> If i have code that works in Acess2000 but when converted to Access 97 it
> >> doesn't, is this likely to be a missing reference? I think the line was
> >> something like DAO.RecordSet.clone but I'm not at the Access97 machine at
> >> the
> >> moment. It certainly had something to do with DAO and an unknown method.
> >>
> >> Dave
>
>
>

I have never actually tried to use DAO 3.6 with Access 97, so I can't say
for certain what problems you might encounter, but as DAO 3.51 was the
version that Access 97 was designed to work with, that is the version I
recommend that you use. It is a simple matter to change the reference.

You will not be able to use linked tables with an Access 97 application and
an Access 2000 or later database, but it does work the other way around - an
Access 2000 (or later) application can link to tables in an Access 97 (or
earlier) database. So, if you need to share data between Access 97 and
Access 2000 or later applications, you need to keep the data in Access 97
format.

Would it be cheaper to upgrade the PC? Well, it depends on the age and specs
of the PC, and also on the complexity of the app. Access 2000 makes
significantly heavier demands on the PC than Access 97. You may find that a
PC that was adequate for an Access 97 app may struggle with Access 2000,
especially if the Access 2000 app includes complex queries and reports.

--
Brendan Reynolds
Access MVP


"David M C" <(E-Mail Removed)> wrote in message
news87DE274-04AA-4EA2-831D-(E-Mail Removed)...
> So Access 97, even with the required DAO module, cannot use DAO 3.6?
> Presumably this is due to a different version of Jet being used?
>
> We have 1 PC that is still on Win98 and Access 97. Looks like it would be
> cheaper to upgrade the PC than go through the hastle of trying to get the
> app
> to work using Access 97. Especially since it doesn't appear to be able to
> connect to an Access 2000 backend either.
>
> Thanks
>
> Dave
>
> "Brendan Reynolds" wrote:
>
>> DAO 3.6 is the wrong version for Access 97, you should have a reference
>> to
>> DAO 3.51
>>
>> The Recordset object has been supported at least since Access 2. (I can't
>> comment on Access 1, as I never used it).
>>
>> If you're still having problems after changing the reference to DAO 3.51,
>> please post the relevant code and a description of what happens when you
>> try
>> to execute the code, including the exact text of any error messages and
>> the
>> error number if any.
>>
>> I do not recommend converting from a later version to Access 97 except in
>> an
>> emergency, i.e. when a user has accidentally converted their only copy of
>> an
>> MDB without realizing the consequences. I definitely do not recommend it
>> as
>> a standard practise.
>>
>> --
>> Brendan Reynolds
>> Access MVP
>>
>> "David M C" <(E-Mail Removed)> wrote in message
>> news:57F9AE74-FED2-4F5D-88EB-(E-Mail Removed)...
>> > OK, it appears Access 97 doesn't support any reference to
>> > DAO.Recordset.
>> > Is
>> > this a Jet 4.0 only feature? The Access 97 machine does have a
>> > reference
>> > to
>> > DAO 3.6.
>> >
>> > Thanks
>> >
>> > Dave
>> >
>> > "David M C" wrote:
>> >
>> >> If i have code that works in Acess2000 but when converted to Access 97
>> >> it
>> >> doesn't, is this likely to be a missing reference? I think the line
>> >> was
>> >> something like DAO.RecordSet.clone but I'm not at the Access97 machine
>> >> at
>> >> the
>> >> moment. It certainly had something to do with DAO and an unknown
>> >> method.
>> >>
>> >> Dave
>>
>>
>>

Are there any disadvantages to using an Access 97 backend and accessing it
using an Access 2000 frontend? The backend only contains the tables.

"Brendan Reynolds" wrote:

> I have never actually tried to use DAO 3.6 with Access 97, so I can't say
> for certain what problems you might encounter, but as DAO 3.51 was the
> version that Access 97 was designed to work with, that is the version I
> recommend that you use. It is a simple matter to change the reference.
>
> You will not be able to use linked tables with an Access 97 application and
> an Access 2000 or later database, but it does work the other way around - an
> Access 2000 (or later) application can link to tables in an Access 97 (or
> earlier) database. So, if you need to share data between Access 97 and
> Access 2000 or later applications, you need to keep the data in Access 97
> format.
>
> Would it be cheaper to upgrade the PC? Well, it depends on the age and specs
> of the PC, and also on the complexity of the app. Access 2000 makes
> significantly heavier demands on the PC than Access 97. You may find that a
> PC that was adequate for an Access 97 app may struggle with Access 2000,
> especially if the Access 2000 app includes complex queries and reports.
>
> --
> Brendan Reynolds
> Access MVP
>
>
> "David M C" <(E-Mail Removed)> wrote in message
> news87DE274-04AA-4EA2-831D-(E-Mail Removed)...
> > So Access 97, even with the required DAO module, cannot use DAO 3.6?
> > Presumably this is due to a different version of Jet being used?
> >
> > We have 1 PC that is still on Win98 and Access 97. Looks like it would be
> > cheaper to upgrade the PC than go through the hastle of trying to get the
> > app
> > to work using Access 97. Especially since it doesn't appear to be able to
> > connect to an Access 2000 backend either.
> >
> > Thanks
> >
> > Dave
> >
> > "Brendan Reynolds" wrote:
> >
> >> DAO 3.6 is the wrong version for Access 97, you should have a reference
> >> to
> >> DAO 3.51
> >>
> >> The Recordset object has been supported at least since Access 2. (I can't
> >> comment on Access 1, as I never used it).
> >>
> >> If you're still having problems after changing the reference to DAO 3.51,
> >> please post the relevant code and a description of what happens when you
> >> try
> >> to execute the code, including the exact text of any error messages and
> >> the
> >> error number if any.
> >>
> >> I do not recommend converting from a later version to Access 97 except in
> >> an
> >> emergency, i.e. when a user has accidentally converted their only copy of
> >> an
> >> MDB without realizing the consequences. I definitely do not recommend it
> >> as
> >> a standard practise.
> >>
> >> --
> >> Brendan Reynolds
> >> Access MVP
> >>
> >> "David M C" <(E-Mail Removed)> wrote in message
> >> news:57F9AE74-FED2-4F5D-88EB-(E-Mail Removed)...
> >> > OK, it appears Access 97 doesn't support any reference to
> >> > DAO.Recordset.
> >> > Is
> >> > this a Jet 4.0 only feature? The Access 97 machine does have a
> >> > reference
> >> > to
> >> > DAO 3.6.
> >> >
> >> > Thanks
> >> >
> >> > Dave
> >> >
> >> > "David M C" wrote:
> >> >
> >> >> If i have code that works in Acess2000 but when converted to Access 97
> >> >> it
> >> >> doesn't, is this likely to be a missing reference? I think the line
> >> >> was
> >> >> something like DAO.RecordSet.clone but I'm not at the Access97 machine
> >> >> at
> >> >> the
> >> >> moment. It certainly had something to do with DAO and an unknown
> >> >> method.
> >> >>
> >> >> Dave
> >>
> >>
> >>
>
>
>

I have been told (by someone who's advice I have reason to respect) that
there is a performance penalty, but I have never found it to be noticeable
in my own experience.

--
Brendan Reynolds
Access MVP

"David M C" <(E-Mail Removed)> wrote in message
news:BA739989-E2CF-48BE-857E-(E-Mail Removed)...
> Are there any disadvantages to using an Access 97 backend and accessing it
> using an Access 2000 frontend? The backend only contains the tables.
>
> "Brendan Reynolds" wrote:
>
>> I have never actually tried to use DAO 3.6 with Access 97, so I can't say
>> for certain what problems you might encounter, but as DAO 3.51 was the
>> version that Access 97 was designed to work with, that is the version I
>> recommend that you use. It is a simple matter to change the reference.
>>
>> You will not be able to use linked tables with an Access 97 application
>> and
>> an Access 2000 or later database, but it does work the other way around -
>> an
>> Access 2000 (or later) application can link to tables in an Access 97 (or
>> earlier) database. So, if you need to share data between Access 97 and
>> Access 2000 or later applications, you need to keep the data in Access 97
>> format.
>>
>> Would it be cheaper to upgrade the PC? Well, it depends on the age and
>> specs
>> of the PC, and also on the complexity of the app. Access 2000 makes
>> significantly heavier demands on the PC than Access 97. You may find that
>> a
>> PC that was adequate for an Access 97 app may struggle with Access 2000,
>> especially if the Access 2000 app includes complex queries and reports.
>>
>> --
>> Brendan Reynolds
>> Access MVP
>>
>>
>> "David M C" <(E-Mail Removed)> wrote in message
>> news87DE274-04AA-4EA2-831D-(E-Mail Removed)...
>> > So Access 97, even with the required DAO module, cannot use DAO 3.6?
>> > Presumably this is due to a different version of Jet being used?
>> >
>> > We have 1 PC that is still on Win98 and Access 97. Looks like it would
>> > be
>> > cheaper to upgrade the PC than go through the hastle of trying to get
>> > the
>> > app
>> > to work using Access 97. Especially since it doesn't appear to be able
>> > to
>> > connect to an Access 2000 backend either.
>> >
>> > Thanks
>> >
>> > Dave
>> >
>> > "Brendan Reynolds" wrote:
>> >
>> >> DAO 3.6 is the wrong version for Access 97, you should have a
>> >> reference
>> >> to
>> >> DAO 3.51
>> >>
>> >> The Recordset object has been supported at least since Access 2. (I
>> >> can't
>> >> comment on Access 1, as I never used it).
>> >>
>> >> If you're still having problems after changing the reference to DAO
>> >> 3.51,
>> >> please post the relevant code and a description of what happens when
>> >> you
>> >> try
>> >> to execute the code, including the exact text of any error messages
>> >> and
>> >> the
>> >> error number if any.
>> >>
>> >> I do not recommend converting from a later version to Access 97 except
>> >> in
>> >> an
>> >> emergency, i.e. when a user has accidentally converted their only copy
>> >> of
>> >> an
>> >> MDB without realizing the consequences. I definitely do not recommend
>> >> it
>> >> as
>> >> a standard practise.
>> >>
>> >> --
>> >> Brendan Reynolds
>> >> Access MVP
>> >>
>> >> "David M C" <(E-Mail Removed)> wrote in message
>> >> news:57F9AE74-FED2-4F5D-88EB-(E-Mail Removed)...
>> >> > OK, it appears Access 97 doesn't support any reference to
>> >> > DAO.Recordset.
>> >> > Is
>> >> > this a Jet 4.0 only feature? The Access 97 machine does have a
>> >> > reference
>> >> > to
>> >> > DAO 3.6.
>> >> >
>> >> > Thanks
>> >> >
>> >> > Dave
>> >> >
>> >> > "David M C" wrote:
>> >> >
>> >> >> If i have code that works in Acess2000 but when converted to Access
>> >> >> 97
>> >> >> it
>> >> >> doesn't, is this likely to be a missing reference? I think the line
>> >> >> was
>> >> >> something like DAO.RecordSet.clone but I'm not at the Access97
>> >> >> machine
>> >> >> at
>> >> >> the
>> >> >> moment. It certainly had something to do with DAO and an unknown
>> >> >> method.
>> >> >>
>> >> >> Dave
>> >>
>> >>
>> >>
>>
>>
>>

David M C <(E-Mail Removed)> wrote:

>Are there any disadvantages to using an Access 97 backend and accessing it
>using an Access 2000 frontend? The backend only contains the tables.

I had a client running 10-15 users on A97 and another 10-15 users on
A2000 against a A97 backend without any problems.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm