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

Converting from Access2K to Access2K3

P: n/a
Hi !

I have many simple, low-tech database applications spread throughout my
organization that I developed in Access 2K..
Most have ODBC for Oracle connections ( read only ) to our principal
application ( a mid size hospital's ADT software ).
My current version of Access is 2000.
I must now decide wether or not to install Access2003 on the PC that I use
to develop these applications.
The users will be converted to 3000 over the next 6 months but there will be
a mix out there of 2K and 2K3.

Are there traps or known issues surrounding this type of situation ?
Is there a FAQ or white paper available ?

Your insights are greatly appreciated.

André Ranger


Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
I have not personally had any problems upgrading from any 2000 to 2003
Access databases. Going from 97 to 2000 through me a loop at first in the
VBA code in that 97 had a default connection method of using DAO and in 2000
that changed to ADO (although DAO is still an option). In 2003, ADO is still
the default.

--
David Hodgkins, MCSD, MCDBA, MCSE
JSTAR Software Solutions
4402 Sweet Cherry Ln.
Kalamazoo, MI 49004
www.jstarsoftware.com - Home of AutoCompact for Access Databases
269-382-2931
"Andy" <so******@hotmail.com> wrote in message
news:Fx**********************@weber.videotron.net. ..
Hi !

I have many simple, low-tech database applications spread throughout my
organization that I developed in Access 2K..
Most have ODBC for Oracle connections ( read only ) to our principal
application ( a mid size hospital's ADT software ).
My current version of Access is 2000.
I must now decide wether or not to install Access2003 on the PC that I use
to develop these applications.
The users will be converted to 3000 over the next 6 months but there will be a mix out there of 2K and 2K3.

Are there traps or known issues surrounding this type of situation ?
Is there a FAQ or white paper available ?

Your insights are greatly appreciated.

André Ranger

Nov 13 '05 #2

P: n/a
On Wed, 6 Apr 2005 10:43:22 -0400, "Andy" <so******@hotmail.com> wrote:
Hi !

I have many simple, low-tech database applications spread throughout my
organization that I developed in Access 2K..
Most have ODBC for Oracle connections ( read only ) to our principal
application ( a mid size hospital's ADT software ).
My current version of Access is 2000.
I must now decide wether or not to install Access2003 on the PC that I use
to develop these applications.
The users will be converted to 3000 over the next 6 months but there will be
a mix out there of 2K and 2K3.

Are there traps or known issues surrounding this type of situation ?
Is there a FAQ or white paper available ?

Your insights are greatly appreciated.

André Ranger


There was a problem in the early months of A2K3 that if you opened an A2Ks or
A2K application in A2K3, it would often crash when you tried to open it in A2K
or A2K2 again. With the more recent service packs for A2K3, this does not
appear to be a problem anymore.

The only other issue might be that A2K had some unique design bugs that were
corrected in A2K2, so you just need to make sure your code is not depending on
any A2K-specific quirks (which is unlikely).
Nov 13 '05 #3

P: n/a
"David Hodgkins" <dh*******@jstarsoftware.com> wrote in
news:bL*****************@fe07.lga:
I have not personally had any problems upgrading from any 2000 to
2003 Access databases. Going from 97 to 2000 through me a loop at
first in the VBA code in that 97 had a default connection method
of using DAO and in 2000 that changed to ADO (although DAO is
still an option). In 2003, ADO is still the default.


I don't get it. Why do people keep saying that?

Converting an A97 MDB to A2K did *not* create an MDB with an ADO but
no DAO reference. It created exactly what you should have expected,
a DAO reference and nothing else.

It's only when you created a new blank A2K MDB and then imported
objects from A97 that you didn't get the DAO reference. Why anyone
would have done that when "converting" from A97 to A2K, I can't
figure.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.