It Likely is a very good idea to keep the version of the database the same
as the actual version of MS access that you use.
when the issue all kinds above fixes and updates for particular version of
MS access, you can bet your bottoms that the code was first tested with the
same version of access.
when you use the older versions, especially in access 2007, then it's going
have to load a different version of the jet database engine, and that's
probably also not a good idea.
It also as a general rule after have some experience in MS access, you'll
quickly find out that there's many advantages to distribute your application
as a mde (or now accDE). The reason why you do that is because your
application runs faster, loads faster, and further more the code cannot
become un compiled which can be a source of databae bloat. an additional
bonus is that un-handeled errors in your code will NOT reset any varibles.
This means that even your global variables will remain intact. this make
your application far more robust and reliable because an error now will not
blow out any of your variables ever, even when you don't have any error
handling code. this means your application becomes reliable and just
soldiers onward and forward even if an error occurs. This is probably the
greatest advantage of using a mde/accde.
In addition your end users will not be able to modify the reprots, form,
code, or even look at your code. So once again makes a lot of sense to
distribute a mde/accde. Users will not be able to accidentally tamper with
your application. Thus this can save you support dollars because somebody
might have modified your code, or modified part of your forms that broke
your application.
I could likey type on for another fifteen to twenty are even 30 to 40 pages
on this whole development process and why we should probably distribute a
mde.
Of course after saying all the above, it's important to realize that you can
only create a mde, or accde by using the same version of MS access that
you're running for development purposes. I don't suppose I should point out
that if you're going to distribute your application to users, then how do
you propose to distribute updates to users, and that also means you'll
likely have to be using a split database.
So for the above reasons, and additional reasons, it certainly makes sense
to distribute and keep your application in the same version that you're
developing with, because any bug or problem you encounter may not occur all
with a different file format that you're currently using.
Of course the other important reason to upgrade is if you keep an old file
format, then you can't use many of the new features in MS access. The reason
why the file format changes with the new version is because additional
features were added into the file format. These changes are not be
compatible with previous versions. These changes allow you to use new
features. Hence, you'll not be able to use the attachment field data type,
or the new multi-valued fields. I've not checked, but is likely a
possibility that integration with sharepoint would also be broken if you
don't upgrade your file formats.
And for 2007, the support for sharepoint is rather nice. If you sign up for
the free office online, then you can install your database on many computers
all over the country, and they will all be sharing the same data back end
(and, you don't have to purchase SQL server, you don't have to purchase
sharepoint, you don't have to purchase a server). You simply don't need any
hardware, but the free office live, and you get a secure multi-user system
for everyone who runs your appliation. So, this sharepoint stuff is rather
amazing.
If you fail to upgrade your formats to the latest version, then you'll be
forfeiting many of the new features that are available in MS access.
