|
Home > Archive > MS Access data conversion > August 2005 > save as Access 97 mdb..
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
save as Access 97 mdb..
|
|
| nycdon 2005-08-01, 1:26 pm |
| I'm using Access 2002, and looking to save an mdb as 97. When I saved as, it
said i needed to set references while IN access 97. Is that correct? I can't
'save as' unless I have access 97?
Any workarounds to this?
Thanks!
Don
| |
| Chris Mills 2005-08-02, 1:24 pm |
| > I'm using Access 2002, and looking to save an mdb as 97. When I saved as, it
> said i needed to set references while IN access 97. Is that correct?
Yes. References ALWAYS need to be checked when converting between versions of
Access. For example, just look at the reference (2002) "Microsoft Access 10.0
Object Library", which in A97 must change to "Microsoft Access 8.0 Object
Library". DAO might change from 3.6 to 3.5. You might have references beyond
the minimum required 3, which may or may not be present. Even if everything
works, your code will at the least be "decompiled".
> I can't
> 'save as' unless I have access 97?
No. You don't need A97 to convert back. You need A97 to test'n'fix after
conversion. If you are thinking of just converting and posting to someone
without testing, don't.
> Any workarounds to this?
No. Workarounds are for bugs. This is not a bug. You are converting between
different "complex" database systems. Access is not at all like Excel or Word
conversions, which are piffling programs <g>.
Alternatively, YES!!! Get rid of as many references as you can!!! Don't use
any "fancy features" and you can reduce an mdb to the minimum requirement of 3
references.
(which will still change, however, but usually automatically)
Chris
| |
| nycdon 2005-08-02, 8:26 pm |
| Thanks Chris..if I bought a 97 upgrade, do you know if could i backward
upgrade from office 2003?
"Chris Mills" wrote:
>
> Yes. References ALWAYS need to be checked when converting between versions of
> Access. For example, just look at the reference (2002) "Microsoft Access 10.0
> Object Library", which in A97 must change to "Microsoft Access 8.0 Object
> Library". DAO might change from 3.6 to 3.5. You might have references beyond
> the minimum required 3, which may or may not be present. Even if everything
> works, your code will at the least be "decompiled".
>
>
> No. You don't need A97 to convert back. You need A97 to test'n'fix after
> conversion. If you are thinking of just converting and posting to someone
> without testing, don't.
>
>
> No. Workarounds are for bugs. This is not a bug. You are converting between
> different "complex" database systems. Access is not at all like Excel or Word
> conversions, which are piffling programs <g>.
>
> Alternatively, YES!!! Get rid of as many references as you can!!! Don't use
> any "fancy features" and you can reduce an mdb to the minimum requirement of 3
> references.
> (which will still change, however, but usually automatically)
>
> Chris
>
>
>
| |
| Chris Mills 2005-08-03, 3:25 am |
| Sorry, I don't know for 2003.
"nycdon" <nycdon@discussions.microsoft.com> wrote in message
news:3E78AB29-6A17-4755-8A6D- FD12B55D961F@microso
ft.com...
> Thanks Chris..if I bought a 97 upgrade, do you know if could i backward
> upgrade from office 2003?
>
|
|
|
|
|