Developing in Access 2003 Deploy in Access 2000

[Jim D.]

Is there a problem with developing my application using Access 2003 (with
Access 2000 file format set) and then moving it to my Access 2000 development
machine, compiling it and then saving it as an mde file and then deploying it
to my customers?

The reason I want to do this is to minimize the need to distribute the
Access XP or 2003 runtime - most of my customers have at least Access 2000.
Plus, I want to minimize dll updates on the client computers.

Thanks for the help.

 

[Brendan Reynolds]

You have to be careful not to use any new features that were not supported
in the earlier version, but other than that, no, there's no great problem.

 

[Jim D.]

Thank you. I remember reading somewhere that when you are in Access 2000
file format mode in Access XP or 2003, you will not be presented with
features that are not available in 2000. Is this true? What might be the
exceptions? I guess I could set a reference in code to a newer dll like ADO
and use a method or property that is not available in the older version of
ADO.

 

[Brendan Reynolds]

No, that is not true.

The ADO example is not really a good example, as ADO is external to Access.
Better examples would be the .AddItem and .RemoveItem methods of combo boxes
and list boxes, or the OpenArgs argument of the DoCmd.OpenReport method, or
the ImportXML and ExportXML methods.

 

[Albert D. Kallal]

Is there a problem with developing my application using Access 2003 (with
Access 2000 file format set) and then moving it to my Access 2000
development
machine, compiling it and then saving it as an mde file and then deploying
it
to my customers?

I am doing the above, as I really do like a2003. I also don't want to have
to have a2000 installed.

The reason I want to do this is to minimize the need to distribute the
Access XP or 2003 runtime - most of my customers have at least Access
2000.
Plus, I want to minimize dll updates on the client computers.

Me too. One thing I have frequently noticed is that after moving the mdb to
the machine with a2000 on it, and then creating the mde, it OFTEN has
problems. So, MAKE SURE you do a de-compile, exit, then re-enter the
appctoion. whack-ctrl-g, and then compile the project. Now do a compact and
repair. Now, you can safely distribute, or create the mde, and distribute
that.

So, about the only thing you have to be aware of here is to do a de-compile
on the machine with a2000...and then re-compile the application. if you miss
this step, I had some real nasty things happen (listboxes, combo boxes etc.
not drawing etc.).

 

[sjl]

I'd like to jump in here because I have the exact same question/issue that
Jim D. originally asked (I want to develop for my client who has A2000 on my
A2002 workstation). It sounds like, no matter what, we need an A2000
install to do a final compile before distributing?

Is there no easy/clean way to develop on A2002/A2003 and distribute an A2000
database without fighting missing references on the client's environment?

Thanks,
sjl

 

[Albert D. Kallal]

I'd like to jump in here because I have the exact same question/issue that
Jim D. originally asked (I want to develop for my client who has A2000 on
my A2002 workstation). It sounds like, no matter what, we need an A2000
install to do a final compile before distributing?

Well, the default file format for a2003 is a2000. So, in theory, you can,
and should be able to work on the a2000 file, and give it to a client
without any problems. However, most good developers ALWAYS distribute a mde
to the users. And, point of fact, you can ONLY create a MDE in the version
of ms-access that you are using. I am only saying to be 100% sure, you want
to do the decompile I suggested. However, this de-compile is NOT a
requirement, but only my quest to reduce problems. I seen some problems if
you don't do the de-compile (this could be a problem that ONLY I
experienced). However, things should just work fine without the de-compile.

Is there no easy/clean way to develop on A2002/A2003 and distribute an
A2000 database without fighting missing references on the client's
environment?

Well, references is a different issue now. If you JUST have the basic min
refs (create a blank new mdb, and take a look at the refs). If you don't
add, or change any of the refs, then you should be trouble free here. And,
of course any developer worth their salt will ALWAYS use late binding for
word, or excel, or Outlook automaton code. I distributed a lot of code to a
LOT of machines, and have not had a broken ref for years now...

 

[sjl]

Albert,
The primary issue I am having relates to the MS Access Object Library. I'm
developing a 2000 version db on a 2002(XP) machine. When I compile my app,
its referencing the 10.0 Object Library. When I ship that to my client,
that library doesn't exist and the reference automatically switches to the
9.0 Object Library. However, in doing so, nothing works until the app is
compiled using 9.0.

As you stated, I have found that compiling my app on a A2000 machine
pointing to 9.0 prior to delivery solves the problem. I'm just wondering if
this is a required step or is there any way to accomplish this on my
A2002(XP) machine prior to delivery? The user doesn't have the 10.0 Object
Library. They only have A2000 (9.0). It sounds like regardless of whether
I want to distribute a locked down .mdb file or an .mde file, I still have
to have an instance of A2000 to do a final compile on before distribution?

Thanks,
sjl

 

[Andy G]

I agree 100% with 'sjl'!!!! The reference problems with a2000 to a2003 is a
pain. Either dropping references and access trying to be too smart and
adding them. I have a2003 installed on my machine (along w/ a2000 and a97)
and any time I try to open a a2000 database using my a2000 version it picks
up new references from the a2003 version. References are ALWAYS a big issue
in coversion, and anyone that tells you different hasn't had the experience
w/ the problems or is in reference denial.

 

[³ÂÌÎ]

²»¶®

 

[bai]

I agree 100% with 'sjl'!!!! The reference problems with a2000 to a2003 is a
pain. Either dropping references and access trying to be too smart and
adding them. I have a2003 installed on my machine (along w/ a2000 and a97)
and any time I try to open a a2000 database using my a2000 version it picks
up new references from the a2003 version. References are ALWAYS a big issue
in coversion, and anyone that tells you different hasn't had the experience
w/ the problems or is in reference denial.




b cxbhdfhjjghjgf