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

Access 97 to Access 2003

P: n/a
Tom
Am about to upgrade several machines running access 97 to new boxes with
access 2003. Got a massive access front end DB with a SQL back end. Guess
I will have to "upgrade" that '97 front.

Anyone have any advice or things to watch out for? Any VBA hasles? Horror
stories??

Hope it goes seamlessly... Got enough headaches.
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Hi Tom.

This link contains our experience with upgrading Access.
It does not address the SQL Server aspects, but does describe
Setup, Conversion, and Usability issues:
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.

"Tom" <ha********@hotmail.com> wrote in message
news:zS**************@newsread1.dllstx09.us.to.ver io.net...
Am about to upgrade several machines running access 97 to new boxes with
access 2003. Got a massive access front end DB with a SQL back end.
Guess
I will have to "upgrade" that '97 front.

Anyone have any advice or things to watch out for? Any VBA hasles?
Horror
stories??

Hope it goes seamlessly... Got enough headaches.

Nov 13 '05 #2

P: n/a
Slight differences between the Jet 3.5 and Jet 4 connections to MSSQL.

Firstly, identity insert works seamlessly like in Access :~) And Unicode
support :~). But transactions even more broken with locking problems.

(david)
"Tom" <ha********@hotmail.com> wrote in message
news:zS**************@newsread1.dllstx09.us.to.ver io.net...
Am about to upgrade several machines running access 97 to new boxes with
access 2003. Got a massive access front end DB with a SQL back end. Guess I will have to "upgrade" that '97 front.

Anyone have any advice or things to watch out for? Any VBA hasles? Horror stories??

Hope it goes seamlessly... Got enough headaches.

Nov 13 '05 #3

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
This link contains our experience with upgrading Access.
It does not address the SQL Server aspects, but does describe
Setup, Conversion, and Usability issues:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html


Allen,

When I run the decompile routine on my A97 file I get an error telling me
that the file is already in use (it isn't) and that the version of VBA used
to create the code doesn't match what's on my PC. I've recently been given
a new PC but it still has our 'standard' corporate image on it.

I'm not sure where to go from here, any polite suggestions? :o)

Regards,
Keith.
Nov 13 '05 #4

P: n/a
Hi Keith

First up, close Access, and make sure there is no ldb file in the same
folder as your mdb. The ldb contains locking information. Access normally
deletes it, but if the computer/application crashes, you can be left with
spurious locking info that has to be deleted manually.

If that does not solve the problem, try creating a new, blank, A97 database
(File | New) in A97, and then import all the objects from the damaged one
(File | Get External | Import).

BTW, my ISP is having problems with their news server, so I'm not able to
get back for quick replies at present.

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

"Keith Wilby" <ke*********@AwayWithYerCrap.com> wrote in message
news:Xn************************@10.15.188.42...
"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
This link contains our experience with upgrading Access.
It does not address the SQL Server aspects, but does describe
Setup, Conversion, and Usability issues:
Converting from Access 97 to 2000, 2002 or 2003
at:
http://members.iinet.net.au/~allenbrowne/ser-48.html


Allen,

When I run the decompile routine on my A97 file I get an error telling me
that the file is already in use (it isn't) and that the version of VBA
used
to create the code doesn't match what's on my PC. I've recently been
given
a new PC but it still has our 'standard' corporate image on it.

I'm not sure where to go from here, any polite suggestions? :o)

Regards,
Keith.

Nov 13 '05 #5

P: n/a
"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
First up, close Access, and make sure there is no ldb file in the same
folder as your mdb. The ldb contains locking information. Access
normally deletes it, but if the computer/application crashes, you can
be left with spurious locking info that has to be deleted manually.

If that does not solve the problem, try creating a new, blank, A97
database (File | New) in A97, and then import all the objects from the
damaged one (File | Get External | Import).


Thanks Allen :o)
Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.