2000 ADEs don't work in XP

  • Thread starter Thread starter dmu
  • Start date Start date
D

dmu

Hi,

All my front ends have been developed in Access 2000 (back end is SQL 2000)
and then made into ades, and now we have a department running Office XP.
When they try to run the ades they get various errors, ranging from "91
Object variable or With block variable not set" to "Microsoft Access has
encountered a problem and needs to close ... Please tell Microsoft about
this problem"

The startup form on most of these front ends are the same basic form and
code, so I don't even understand why I get differing errors. If I open the
Access 2000 adps in Access XP, convert to 2002, made a new ade without
changing anything, the new ades work fine.

I don't want to be maintaining separate projects and ades for 2000 and XP
when the underlying projects are the same. Can someone point me in the
right direction for a better solution?

Thanks!

-dmu
 
Sorry, but I believe your only option is to convert the ADP to Access 2002
and then recreate the ADE.

Note, though, that you really don't need to maintain separate versions of
the ADP. Do all of your work in the Access 2000 version, and when you're
done, convert a copy of it to Access 2002 before creating the ADE.
 
d> All my front ends have been developed in Access
d> 2000 (back end is SQL 2000) and then made into
d> ades, and now we have a department running Office
d> XP. When they try to run the ades they get various
d> errors, ranging from "91 Object variable or With
d> block variable not set" to "Microsoft Access has
d> encountered a problem and needs to close ... Please
d> tell Microsoft about this problem"

I would open support incident with Microsoft (against access 2002, not
access 2000), sent them the adp file, and asked them to complile it into a
2000' ade that would not crash in access 2002. Insist that they don't just
give some advise but actually compile the adp in access 2000 and give you
the ade.

Vadim
 
Thanks Doug. Have started to do so.

-dmu


Douglas J. Steele said:
Sorry, but I believe your only option is to convert the ADP to Access 2002
and then recreate the ADE.

Note, though, that you really don't need to maintain separate versions of
the ADP. Do all of your work in the Access 2000 version, and when you're
done, convert a copy of it to Access 2002 before creating the ADE.
Click to expand...
 
Thanks Vadim. I don't think if I want to deal with Microsoft at this time
though. I'm able to convert to 2002 and create new ades, and I don't think
I want to send them 18 adps to compile - (would they even be able to do make
the ades without having the SQL databases?), and then have to send more
files to them every time I make a change.

-dmu
 
d> Thanks Vadim. I don't think if I want to deal with
d> Microsoft at this time though. I'm able to convert
d> to 2002 and create new ades, and I don't think I
d> want to send them 18 adps to compile - (would they
d> even be able to do make the ades without having the
d> SQL databases?), and then have to send more files
d> to them every time I make a change.

Most likely one file would be enough, perhaps with the database backup that
they would restore. If they find the problem and provide the walkaround,
most likely it would work with all other adp's as well.

Vadim
 
Back
Top