D
Deb
Will be converting to Access 2003 from Access 2000 soon. Have several large
databases. Any known issues I should be aware of??
Thanks!
databases. Any known issues I should be aware of??
Thanks!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
V
Van T. Dinh
You don't even need to convert the databases!
Access 2003 can use databases in Access 2000 file format natively.
Access 2003 can use databases in Access 2000 file format natively.
C
Chris Mills
Provided you're happy with a decompiled state, surely? After all, the
references MUST change.
Chris
references MUST change.
Chris
D
david epsom dot com dot au
Form and Report module public variables are no longer
available as Form/Report properties for use in a control
source or record source.
I'm still not 100% convinced about the practical compatibility
of A2K MDE's on A2003 (obviously, doesn't work the other way
at all).
And I still seem to have occasional problems converting
from A2003 back to A2K.
(david)
available as Form/Report properties for use in a control
source or record source.
I'm still not 100% convinced about the practical compatibility
of A2K MDE's on A2003 (obviously, doesn't work the other way
at all).
And I still seem to have occasional problems converting
from A2003 back to A2K.
(david)
C
Chris Mills
I'm still not 100% convinced about the practical compatibility
Deb,
It's claimed there need be no changes at all, after all A2000 format IS native
to later versions.
But I would, as a matter of course, Decompile/Compile/Repair/Compact an app
before shifting it to another version (and afterwards). There could be subtle
corruptions in it ... and though "conversions" tend to be automatic, not so if
there are any "unspecified corruptions".
If you use any more than the 3 (I think) required references, you may need to
check them.
I assume you have purchased (or are happy with) the "Digital Certificate"
arrangements and pesky warnings.
(I don't have direct knowledge of A2003, just A2002 and "downwards" from
there)
Chris
I was only thinking of mdb's when I said references MUST change.of A2K MDE's on A2003 (obviously, doesn't work the other way
at all).
Deb,
It's claimed there need be no changes at all, after all A2000 format IS native
to later versions.
But I would, as a matter of course, Decompile/Compile/Repair/Compact an app
before shifting it to another version (and afterwards). There could be subtle
corruptions in it ... and though "conversions" tend to be automatic, not so if
there are any "unspecified corruptions".
If you use any more than the 3 (I think) required references, you may need to
check them.
I assume you have purchased (or are happy with) the "Digital Certificate"
arrangements and pesky warnings.
(I don't have direct knowledge of A2003, just A2002 and "downwards" from
there)
Chris
V
Van T. Dinh
I I couldn't remember exactly but I have just tried using A2K2 to open 2
databases in A2000 file format that have never been opened by A2K2. One of
these was originally written in Access 2.0.
Access 2002 seems to know the old References and changes References to the
new version (from Office 9.0 to Office 10.0 Library) correctly. I am not
sure about ADO both databases used JET Back-Ends and I prefer to use DAO
with JET Back-Ends. DAO 3.6 is the same for both A2K & A2K2.
I guess if you have added other References besides the standard References,
these need to be changed if required.
Both databases seem to work fine in A2000-file-format (before and after
re-compiling), i.e. no conversion to A2K2 file format is required.
databases in A2000 file format that have never been opened by A2K2. One of
these was originally written in Access 2.0.
Access 2002 seems to know the old References and changes References to the
new version (from Office 9.0 to Office 10.0 Library) correctly. I am not
sure about ADO both databases used JET Back-Ends and I prefer to use DAO
with JET Back-Ends. DAO 3.6 is the same for both A2K & A2K2.
I guess if you have added other References besides the standard References,
these need to be changed if required.
Both databases seem to work fine in A2000-file-format (before and after
re-compiling), i.e. no conversion to A2K2 file format is required.
C
Chris Mills
I had no intention of putting you to so much trouble, Van!
I just thought it was worthwhile pointing out that an mdb (ANY mdb) might
benefit from compiling when running on a new version of Access!
Regards
Chris
I just thought it was worthwhile pointing out that an mdb (ANY mdb) might
benefit from compiling when running on a new version of Access!
Regards
Chris
C
Chris Mills
My point was, Access certainly fixes up standard references automatically, but
only if there was no corruption or other errors in a conversion. (in my
experience)
only if there was no corruption or other errors in a conversion. (in my
experience)
V
Van T. Dinh
No problems. I need my memory refreshed occasionally (old age has caught up
finally).
Completely agree with you regarding re-compiling. Whever, I publish a new
version of my databases, I always relink Tables, check References,
Re-Compile, Compact & Repair and finally Make MDE for publication.
finally).
Completely agree with you regarding re-compiling. Whever, I publish a new
version of my databases, I always relink Tables, check References,
Re-Compile, Compact & Repair and finally Make MDE for publication.
S
sunqiuxia
dsakjflkjalskdfj;lasd
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.