By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,631 Members | 892 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,631 IT Pros & Developers. It's quick & easy.

Access 97 to 2003 General Question

P: n/a
I am running an Access 97 (Office 97 Pro) application on an
older computer, and am about to be upgraded so my computer,
and installed software, matches the rest of the office

That means going to MS Office 2003 Professional, so my A97
application may be updated and shared with another computer

This application uses a macro I wrote to "import delimited"
from a text file (c:\scanner\receive.txt) and then uses a
few selection screens and MANY reports based on queries

I don't EXPECT any particular problems letting A2003 do the
conversion from A97 - but thought I'd ask first to see if
there are any particular "gotcha's" going from 97 to 2003

John Thomas Smith
http://www.direct2usales.com
http://www.pacifier.com/~jtsmith
Jul 7 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
John Thomas Smith <jt*****@pacifier.comwrote in
news:80********************************@4ax.com:
I don't EXPECT any particular problems letting A2003 do the
conversion from A97 - but thought I'd ask first to see if
there are any particular "gotcha's" going from 97 to 2003
There usually are none, except for some extremely tricky issues that
are going to be very, very uncommon. I can't think of anything
except the one of referring from a subform to fields in the parent
form's recordsource. In A97 that works fine, in A2K and after, it
causes terrible problems. The solution is to have a hidden control
in the parent form with the data and refer to the control instead of
the underlying field. I spent a helluva lot of time working out the
solution to that one, but once you know it, it's easy to implement.

But it's not exactly a common practice, so unlikely to cause a
problem.

Try the conversion and see if any problems result. We can help you
resolve any issues that arise.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 7 '06 #2

P: n/a
The conversion will probably be fine, but here's a list of potential setup
issues, conversion issues, and usebility issues after conversion:
Converting from Access 97
at:
http://allenbrowne.com/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.

"John Thomas Smith" <jt*****@pacifier.comwrote in message
news:80********************************@4ax.com...
>I am running an Access 97 (Office 97 Pro) application on an
older computer, and am about to be upgraded so my computer,
and installed software, matches the rest of the office

That means going to MS Office 2003 Professional, so my A97
application may be updated and shared with another computer

This application uses a macro I wrote to "import delimited"
from a text file (c:\scanner\receive.txt) and then uses a
few selection screens and MANY reports based on queries

I don't EXPECT any particular problems letting A2003 do the
conversion from A97 - but thought I'd ask first to see if
there are any particular "gotcha's" going from 97 to 2003

John Thomas Smith
http://www.direct2usales.com
http://www.pacifier.com/~jtsmith

Jul 8 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Browse more Microsoft Access / VBA Questions on Bytes