|
Home > Archive > MS Access data conversion > November 2005 > Conversion from Access 2002 to Access 2003
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 |
Conversion from Access 2002 to Access 2003
|
|
|
| Are there any issues or concerns I should be aware of in converting from
Access 2002 to Access 2003. I have done fairly extensive VBA programming of
a large database and don't want to run into issues with converting. Any
help/comments would be appreciated.
Thanks
Carl
| |
| Allen Browne 2005-11-25, 3:24 am |
| Should be fine, Karl. The database should convert without issue.
You could run into problems with references if you use MS Graph, Calendar
control, or references to other Office products such as Outlook 10. If you
find your code or functions don't work, open any code window and choose
References on the Tools menu. Replace the old reference with the correct one
for the new version. More on references:
http://allenbrowne.com/ser-38.html
If you have not used A2003 before, you may be surprised at how Microsoft
tries to persuade you NOT to open your databases any more. You have to
navigate through a series of long-winded and unintuitive dialogs, choosing
the non-default answers, every time you want to open your file. You can
avoid this nonsense by setting Macro Security to Low in A2003 under:
Tools | Macro Security.
These settings might make sense if you are accepting databases from people
you don't know, but the make absolutely no sense for the average user.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Carl" <Carl@discussions.microsoft.com> wrote in message
news:437E5B51-8591-4C56-AFC2- 80EBFE98C0B8@microso
ft.com...
> Are there any issues or concerns I should be aware of in converting from
> Access 2002 to Access 2003. I have done fairly extensive VBA programming
> of
> a large database and don't want to run into issues with converting. Any
> help/comments would be appreciated.
>
> Thanks
> Carl
| |
|
| Thanks Allen - this helps. I haven't decided whether to upgrade to Office
2003 or not but this may help make up my mind.
Carl
"Allen Browne" wrote:
> Should be fine, Karl. The database should convert without issue.
>
> You could run into problems with references if you use MS Graph, Calendar
> control, or references to other Office products such as Outlook 10. If you
> find your code or functions don't work, open any code window and choose
> References on the Tools menu. Replace the old reference with the correct one
> for the new version. More on references:
> http://allenbrowne.com/ser-38.html
>
> If you have not used A2003 before, you may be surprised at how Microsoft
> tries to persuade you NOT to open your databases any more. You have to
> navigate through a series of long-winded and unintuitive dialogs, choosing
> the non-default answers, every time you want to open your file. You can
> avoid this nonsense by setting Macro Security to Low in A2003 under:
> Tools | Macro Security.
> These settings might make sense if you are accepting databases from people
> you don't know, but the make absolutely no sense for the average user.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Carl" <Carl@discussions.microsoft.com> wrote in message
> news:437E5B51-8591-4C56-AFC2- 80EBFE98C0B8@microso
ft.com...
>
>
>
|
|
|
|
|