Hi.
We have been using an application that was developed by a programmer using
MS 97. The application is just fine, but we are getting some new computers
that are using A2K some even A2K3. Someone has told me that by using these
new versions of Access, I could run into run-time problems and even
corrupting the files. This application has Visual Basic Code (Customized
Reports, Module Coding, Macros, etc..) I need if there is anything that I can
do to avoid any potential problems.... I forgot to mentioned that the
developer is no longer around....so I need your assistance/advise...

mxinter

Take a look at this article:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html

--
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.

"mxinter" <(E-Mail Removed)> wrote in message
news:E3F0DD95-1166-497F-BBC9-(E-Mail Removed)...
> Hi.
> We have been using an application that was developed by a programmer using
> MS 97. The application is just fine, but we are getting some new computers
> that are using A2K some even A2K3. Someone has told me that by using these
> new versions of Access, I could run into run-time problems and even
> corrupting the files. This application has Visual Basic Code (Customized
> Reports, Module Coding, Macros, etc..) I need if there is anything that I
> can
> do to avoid any potential problems.... I forgot to mentioned that the
> developer is no longer around....so I need your assistance/advise...
>
> mxinter