Should there be any problems developing in Access 2003 for customers using
Access2000?
I am not sure, but I have a suspicion that they have more problems in the
network after I started developing in 2003.
regards
reidarT
I find that developing with a2003 (with a2000 format) works very well.
However, two things:
You REALLY REALLY need to do a de-compile, BEFORE you convert the
application to a mde. Of course, you do convert the final application to a
mde? This of course needs to be done on a pc with access 2000.
I have found that if I take the a2000 file (with lots of development done in
a2003), to a pc with a2000, then a good bunch of bugs seem to crop up (combo
boxes..and some sub=forms just don't work right). However, AFTER moving the
file to a pc with a2000, you then need to de-compile. (then exit). And then
re-enter...view some code and re-compile. If you do this then the a2000
users will be just fine.
If you don't..I find the resulting mdb (and mde!!) files are not stable.
So, do the de-compile..and re-compile (do this even if you are NOT going to
use a mde..but *still* do this even when you are using a mde!!).
